Dashboards

A dashboard is a durable HTML artifact built by an agent. Use it when people should return to the current output rather than read through a conversation to find the latest result.

Creating a dashboard starts its first build immediately. You provide a title, optional description, instructions, model, reasoning level, and optional project. If no project is chosen, d5s creates an unlisted one for the dashboard.

Refreshable material

Dashboard instructions describe the audience, data to use, questions to answer, and presentation the agent should produce. The dashboard run mode adds the product's artifact rules so the agent creates a self-contained, safely renderable result.

The app currently creates dashboards with manual refresh. Choose Refresh to start a new dashboard session. Open the chat panel to see the build conversation, follow progress, or ask the agent to update the dashboard. Completed agent responses use the same personal feedback controls as chats, including an optional details dialog. The chat panel shows only your own selection, not teammate ratings or aggregate counts. Each accepted update can publish another materialized version.

The beta API also models scheduled refresh fields. Treat those as an integration surface rather than assuming every scheduling control is available in the current dashboard UI.

Rename a dashboard

Choose Rename from a dashboard's actions menu, on the Dashboards list, a project's Dashboards strip, or the dashboard page itself. The title is configuration rather than build output, so it stays editable while a build is running and after one fails.

Renaming also retitles the dashboard's build sessions, so the same name appears wherever those sessions are listed. If the dashboard is backed by an unlisted project, that project is renamed too — so promoting it later surfaces the current name rather than the one you first typed. A dashboard inside a project you named yourself never renames that project.

Versions keep history

The latest successful artifact is the live dashboard. Earlier materialized versions remain available from the version menu. Preview a previous version to compare it; choose Restore to make it live again without asking the agent to rebuild it.

Build sessions and versions solve different problems. A session explains what the agent did and why a build failed. A version is the rendered output people consume. Deleting a dashboard preserves its past build sessions, while restoring changes which stored artifact is live.

The project supplies reusable instructions, memory, files, skills, connectors, and access. The dashboard owns its build instructions, live artifact pointer, refresh history, and versions.