Appearance
Dashboard
The Dashboard is your home view — a single page that answers "what is the orchestrator doing right now, and how did recent runs go?" Every row in its table is a record: one ticket the orchestrator picked up and worked (or is working) through the workflow. If you only keep one page open, it's this one.
Use the Dashboard to:
- Check what's running right now and how far along each run is.
- Spot failures quickly and jump into the details.
- Find a past run by ticket title, id, Lane, or state.
- Start a new Lane (the New Lane button, top right).
The stat cards
Four cards across the top give you the orchestrator's pulse:
| Card | What it shows |
|---|---|
| Active | Runs in progress — anything that hasn't finished yet (Picked Up through Notifying). |
| Completed | Runs that finished successfully (state Done). |
| Success rate | Done ÷ all finished runs (Done + Failed + Cancelled). Shows — until at least one run has finished. |
| Total spend | Combined API cost (USD) reported by the runs loaded on this page. Runs on subscription auth report $0. |
The cards summarize the records loaded into the page (the most recent 100) — they don't change when you apply filters below.
The records table
One row per record, newest activity first:
| Column | Meaning |
|---|---|
| Lane | The Lane that picked up the ticket. |
| Ticket | The ticket's title and external id (e.g. the GitHub issue number). |
| State | Where the run is in the workflow — see the state guide below. |
| Model | The Claude model the run used (e.g. Opus 4.8, Haiku 4.5). |
| Updated | The last time anything happened on this record, in your local time. |
| Duration | Total wall-clock time. Still counting for active runs; final time for finished ones. |
Click any row to open the Record Detail view — live logs, the phase stepper, the event timeline, generated artifacts (PRD, design, QA report), PR links, and the Cancel / Rerun actions. The Dashboard is the overview; Record Detail is where you investigate one run.
Understanding states
The colored pill in the State column tells you where a run is:
| State | What's happening | Anything to do? |
|---|---|---|
| Picked Up | The ticket matched a Lane and a record was created. | No — it advances on its own. |
| Queued | Waiting for a free run slot (concurrency caps), or — on an Optimize Lane — for artifacts to be ready. | No — it's admitted as slots free up. |
| Starting | Workspace and runner are being provisioned. | No. |
| Planning | The PM agent is turning the ticket into a requirements doc (PRD). | No — but you can watch live in Record Detail. |
| Coding | Design, tests, and implementation. Usually the longest state. | No. |
| Reviewing | The QA agent is adversarially reviewing the work. | No. |
| Finalizing | Committing, pushing, and opening the PR. | No. |
| Notifying | Posting the ticket comment / notifications. | No. |
| Done | Finished — a PR is open and waiting for you. | Yes — review the PR. |
| Failed | The run stopped with an error. | Open the record: the failure callout explains why, and Rerun retries it. See Troubleshooting. |
| Cancelled | Someone cancelled the run. | Rerun it if it was cancelled by mistake. |
A run normally flows top to bottom through this list. The orchestrator keeps the human checkpoint at the end: Done means "ready for your code review," not "merged."
Finding a run
Three filters sit above the table and combine with each other:
- Lane — show only one Lane's records.
- State — show only records in one state. Tip: filter on Failed for a quick triage pass.
- Search — type any part of the ticket title or its id.
Clear a filter with the small ✕ in its field.
Data freshness
The Dashboard loads when you open it and updates when you press Refresh (top right) — it does not auto-update. So if you're waiting on an active run, either press Refresh now and then, or open the record itself: Record Detail streams live, with logs and state changes appearing as they happen.
Common questions
A ticket I labeled isn't showing up. The orchestrator checks for new tickets about every 30 seconds, so give it a moment and press Refresh. If it still doesn't appear, walk the checklist in Troubleshooting → No tickets picked up.
A run shows Failed — now what? Click the row. The red callout at the top of Record Detail states the reason (for example, a missing Anthropic credential points you to Settings), and the logs show exactly where it stopped. Fix the cause, then press Rerun — reruns re-fetch the ticket, so edits you made to the ticket are picked up. The triage order is in Troubleshooting.
Duration keeps growing but the state hasn't changed. Coding is genuinely long on real tickets (often many minutes). If a run sits in one state far longer than usual, open the record and check the live log — a stuck run is eventually failed automatically by the orchestrator's watchdog.
Total spend looks too low. Runs using subscription-based Claude auth report $0 cost; the card only adds up what the API reports. Per-run cost lives in Record Detail, and trends live in Analytics.