Dashboard
Sessions & projects
The projects and sessions lists, session-detail tabs, and project sub-pages.
Projects and sessions are the two ways to navigate everything the desktop syncs. A project aggregates all the work in one repository; a session is a single run of an AI agent inside that project. This page walks through both lists and the detail views behind them.
The Projects list
Projects are created automatically from the repositories you work in on the desktop. Each project card shows lifetime rollups across all of its sessions — sessions, prompts, commits, and files changed — plus its total spend and when it was last active. Open a project to reach its dashboard, where you can see recent sessions, set a monthly budget, and jump into its sub-pages.
The Sessions list
The Sessions list is every run across your projects, newest first, with search, a tool filter, and an active/ended toggle. Rows update live as sessions progress, so you can leave the page open and watch status change. Each row can carry several inline chips:
| Chip | What it tells you |
|---|---|
| Status | A live agent-status badge — working, awaiting input, blocked, error, or completed — for active sessions. |
| PR | A pull-request chip (or Draft) linking out to the PR opened from that session. |
| Context health | A 0–100 context-health score, coloured by band (healthy, warning, or critical). |
| Linked issues | Issue keys from Linear, GitHub, Jira, or GitLab tickets tied to the session. |
Note
The PR, context-health, and linked-issue chips depend on the latest cloud schema being provisioned on your deployment. If it isn’t, the session list still renders — you’ll see a note that some details aren’t available yet, but the sessions themselves are complete.
Session detail tabs
Click any session to open its detail view. A row of tabs across the top switches between different lenses on the same run. There are ten tabs:
| Tab | What it shows |
|---|---|
| Activity | The trace-by-trace transcript — each prompt with its tool calls, file edits, sub-agents, and the AI’s response. |
| Timeline | A searchable, filterable stream of every event in the session, grouped by trace. |
| Tasks | The kanban board for this session — To do, In progress, Blocked, and Done. |
| Analytics | Cost, productivity, code-impact, and quality charts scoped to this one session. |
| Checkpoints | Plan-step gates with their diffs, confidence scores, and approve/reject outcomes. |
| Scope | The file-scope boundary for the session and any out-of-scope write violations. |
| DNA | Personal coding-pattern signals derived from the session (tool preferences, timing, failure modes). |
| Intent | Goal-drift detection — how closely the work tracked the stated goal. |
| Rollback | The session’s continuation and decision points, with mental-rollback branch info. |
| Impact | Code-impact analysis — files touched, lines changed, and retention/churn over time. |
Every tab is read-only on the web — you are reviewing what the desktop captured, not steering the agent from here. Use the Share button on the session header to generate a redactable replay link a teammate can watch.
Project sub-pages
A project dashboard links out to focused sub-pages for the parts of the workflow that span multiple sessions:
- Report — a branded, client-ready summary of the project’s work, with a code-redaction mode that hides anything that could leak code.
- Memory — the project’s accumulated decision memory and how it has evolved.
- Orchestration — multi-tool task plans decomposed from a goal, with per-subtask progress.
- Bus — the read-only coordination bus of inter-agent tasks and decision gates.
- Arenas — agent-vs-agent runs of the same goal, with a verdict strip and the human-picked winner.
- Governance — the policy audit feed of guardrail events across the team.
- Budget — the project’s monthly spend against its budget, with alert thresholds.
- Alerts and Handoff — smart alerts and the developer handoff summary for the project.