Mission Control
Read a running multi-agent collaboration, and repair it when it goes quiet.
Mission Control is the orchestration cockpit docked above your terminal grid. It appears the moment a project has a live link or a running orchestration — and renders nothing, and polls nothing, when there is nothing to orchestrate.
The counter row
Every count with something behind it is a button, not a label.
| Counter | What it means | What to do |
|---|---|---|
N links | Active links in this project | Open the Map to see their direction |
N running | Live orchestrations | — |
N voting / N decided | Open and settled swarm decisions | Cancel a decision whose peer disappeared |
N awaiting reply | Delivered, unanswered, peer can answer | Click it, then Nudge a silent peer |
N stuck | Delivered to a peer with no link back | Click it — these never resolve on their own |
N quarantined | Links whose terminal restarted or closed | Relink, or Clear all |
N needs you | An agent finished or is waiting on you | Click the pill to jump to its terminal |
Awaiting reply vs stuck
These look similar and need opposite responses.
Awaiting reply means the peer can answer and has not yet. Usually it is still working. Sometimes it finished, printed its verdict into its own terminal, and never ran the reply command — in which case the sender waits forever while every receipt still reads delivered.
You are the only one who can tell those two apart, which is why each row carries a Nudge button that tells the peer to send the answer it is already holding.
Stuck means the peer was delivered a request with no send-capable edge pointing back. It was told it has no channel, so it did the work and stopped. No amount of patience fixes it — the missing edge has to be created.
That is why stuck is counted separately rather than folded into awaiting reply.
The participant rail
One pill per agent, showing:
- The agent logo and terminal name
- Live status, and an attention marker when it needs you
- Link direction counts —
→2outgoing,←1incoming - Context usage for that agent
Click any pill to jump straight to that terminal. Pills for agents in other projects are marked, since links can cross projects.
Map, Runs, Logs
Three views on the right of the header:
- Map — the live Team Map
- Runs — delegation history
- Logs — run and app logs
Drag the divider under the section to resize it, or collapse it entirely when you want the panes back. Height, collapse state, and selected view are remembered per project. The arrow icon opens the full Orchestration Dashboard on the same tab.
Context meter
Next to the model chip on every terminal tab and pane header there is a context chip: the share of that agent's context window the last turn used. The same figure rides the Mission Control pills and the Team Map cards.
This matters more in a team than solo. When you are about to hand off a large review, the pill reading ~29% is a better target than the one reading ~104%. A figure over 100% means the last turn exceeded the recorded window for that model — treat it as a signal to start a fresh terminal.
Attention Inbox
Agents that finish, or stop and wait, surface in the activity feed with a detail line carrying the assistant's last message — so you can tell a finished run from one parked on a question without opening it. Click an entry to land in that terminal.
The same signal appears as the N needs you count on the Mission Control rail. It does not duplicate the completion notifications you already receive.
Recovering after a restart
Restarting the app quarantines every link, because the terminals they pointed at are gone. Recovery is two steps.
1. Restore the sessions
In Resume AI Sessions, sessions that ran as one linked team appear under an Agent team banner — "2 of these sessions worked together" — with the agent chain and how long ago it ran.
Resume this agent team brings every member back in one confirmation. Individual sessions carry a team chip, so you can tell a collaborative session from a solo one.
2. Restore the links
With the terminals running, Mission Control shows Resume team next to the quarantined count. It relinks every revivable link in the project and wakes each participant with the fact it is blocked on — an owed reply command, a status board, or a restored edge.
Each terminal gets a single catch-up notice, not one per link.
Links whose terminals are gone for good are cleaned up rather than piling up in the quarantined counter forever.
Next
- Team Map — read the collaboration as a graph
- Linked Terminals — how delegation and reply edges work