The dashboard queues work, renders state, and keeps operators oriented. It intentionally does not replace the local execution loop.
The dashboard is the visibility layer for the agents ecosystem. It reads state from Convex, dispatches queued work, and lets you inspect the lifecycle of threads, sessions, skills, previews, annotations, and settings.
Core routes
| Route | Purpose | Source |
|---|---|---|
/ | Activity summary plus cards for projects, sessions, skills, and actions | apps/app/src/app/page.tsx |
/projects | Project registry with list/grid views and add-project entrypoints | apps/app/src/app/projects/page.tsx |
/projects/[name] | Project detail with session rows and session drawer / overlay detail | apps/app/src/app/projects/[name]/page.tsx |
/threads/[id] | Full thread transcript view | apps/app/src/app/threads/[id]/page.tsx |
/skills | Built-in and custom skills catalog | apps/app/src/app/skills/page.tsx |
/previews | Previews and annotations feed | apps/app/src/app/previews/page.tsx |
/search | Search across threads, projects, skills, and sessions | apps/app/src/app/search/page.tsx |
/settings | Backend, agents, appearance, and keys | apps/app/src/app/settings/** |
/install | Install instructions for the CLI and local agent OS | apps/app/src/app/install/page.tsx |
Interaction model
Global overlays are mounted from apps/app/src/components/overlay-root.tsx and keep interactions fast without deep route stacks.
Mobile drawers are powered by vaul and preserve the same information architecture on smaller screens.
Project-session clicks open a detail surface that prefers transcript data and falls back to trace events when needed.
Skills open as an overlay inside the product shell rather than kicking users into a detached docs experience.
Keyboard shortcuts
The footer currently wires several global shortcuts:
- + opens compose
- / opens search
- , opens settings
Source: apps/app/src/components/footer.tsx
Why this matters
The dashboard is intentionally not the orchestrator. It is the operator view over local-first execution. Work is queued in the web UI, but agents work is what actually runs sessions on a machine.