Documentation

Mission Control

The home view — what is running, what needs you, and what is blocked.

Mission Control is where you land. It answers one question: what needs me?

That is a different question from what is happening?, which is what the factory answers. Mission Control is triage; the factory is operations.

What it surfaces

  • work waiting on you — questions to answer, plans to approve, pull requests to review
  • work that is paused or blocked
  • what is currently running
  • recent completions and failures
Agent execution
Running
3 tasks in progress
Agent slots3/10
Queue clears
in about 2h 40m
6 queued
Daily quotaProfessional
11h 20magent time today · no daily limit
HorizonNext 24h
Current work3 live
  • Export invoices as CSV
    QA
  • Fuzzy search in the customer list
    Developer
  • Onboarding checklist for new teams
    Architect
Run log
  1. Reviewer approved “Dark mode for settings”
  2. QA verified 5 of 5 criteria on “Invoice PDF footer”
  3. QA sent “Search filters” back: criterion 3 unmet
  4. Architect started “Onboarding checklist”
Up next6
  • Retry failed webhook deliveriesP1
  • Upgrade the date libraryP2

Mission Control: agent slots, what is running, what is next and what just happened. Illustrative data.

Paused work is the important part

The most valuable thing here is work that has stopped and is waiting on a human.

A task in NEEDS_HUMAN_REVIEW has hit a decision only you can make. Until you answer, it holds no agent slot and makes no progress — but it also does not announce itself anywhere else. Mission Control is where it becomes visible, and paused work can be resumed directly from here.

An organization with several paused tasks nobody noticed has capacity sitting idle and people waiting on results that will never arrive.

A daily rhythm

  1. Answer anything asking a question. Cheapest possible intervention, unblocks work immediately.
  2. Approve or revise waiting plans. Cheapest point to change an approach.
  3. Review finished pull requests.
  4. Glance at failures. One-off failures are noise; the same failure at the same stage across unrelated tasks is a configuration problem — see When a task gets stuck or fails.

You should not need to watch it

Notifications exist so Mission Control is somewhere you go deliberately rather than somewhere you monitor. The bell in the header tells you when work needs you, such as a task waiting for review or a failed task. There is nothing to turn on. See Notifications.

In this section