Dashboard

The Dashboard is the view Command Center opens on and the one you return to between tasks. It answers four questions on one screen: what just happened (Live), what does my system contain (Infrastructure), is everything running (Platform Health), and what am I steering toward (Mission Control and your pinned routines).

The header shows the workspace root the app is operating on — if that path is wrong, fix it in Settings ▸ Project before anything else.

Live — the activity feed

The wide panel on the left streams recent events: file creations and edits, routine runs, daemon state transitions, mission updates, and session starts. It is how you notice agent work landing without watching a terminal.

• Click a file event to reveal that file in Documents. Shift-click (or the ⧉ icon on hover) opens it in a new Documents window instead.
• Log opens the full Activity Log — the durable, filterable history behind this box.
• Clear empties the box only. Nothing is deleted; the history stays in the Activity Log until its retention window removes it.

Infrastructure — what the system contains

The middle panel shows live counts of the working parts in your workspace: agents, protocols, active missions, MCP servers, skills, and report documents. Each row is a shortcut — click it to jump to the owning view (the Missions row opens the missions log directly). The MCP Servers row carries a health badge summarizing how many servers are currently reachable.

If every count shows as unknown, the workspace root is not resolving — check Settings ▸ Project.

Platform Health — daemon control

The right panel is the control surface for the background services the platform runs on. One row per service, re-probed every 10 seconds:

For the app-managed services each row offers:

• Start / Stop — starts or stops that one service. The rest of the app keeps running; views that depend on a stopped service simply show offline.
• Autostart toggle — whether the service launches with the app. This is a hot setting; it persists to the runtime config (see the configuration reference) and applies from the next launch.
• Click the row to jump to the view that owns the service.

When a view elsewhere in the app reports "daemon offline", this panel is where you start it. If a service refuses to come up, run Doctor — it probes the same services with fix actions attached.

Mission Control — the strategic files

The full-width band below the status strip surfaces your standing strategic files — the context, directives, and missions log every agent session reads — plus any notes you keep alongside them. You can read and edit them inline without leaving the Dashboard; the same files are the home surface of the Missions Board. See missions and the fleet for what these files mean and how agents consume them.

Routines — your pinned set

The bottom section lists your favorited routines only, by design — the full catalog lives in the Routines view, and you star the ones you want on the Dashboard from there. Each row is the same live control you get in the Routines view: run and stop, the schedule control, model and status, and the star itself.

A badge next to the section heading shows whether the routines daemon is online. When it is offline the section explains itself: start the daemon from the Routines view or from Platform Health above. When no routine is starred yet, the empty state points you to the Routines view to pin some.

See routines and automation for the model behind scheduled agent work.

Related pages

• Activity Log — the durable history behind the Live feed
• Doctor — health checks with one-click fixes
• Settings — where the wiring behind this screen is configured
• The operator model — why the Dashboard reads the way it does