Desktop App
Mission Control
The Global Home fleet view, the needs-attention queue, and the agent question inbox.
When you run more than one AI session at a time, the hard part is not starting them — it is knowing which one needs you right now. Mission Control is the Home view of the desktop app, and it is built for exactly that. It is a live control tower over every active session across all your projects, with the ones waiting on you pulled to the top.
Note
Mission Control is the Home entry in the sidebar, at the project-list level. It updates in place as your sessions change state — you do not need to refresh it.
The fleet
The fleet is a grid of cards, one per active session, across every project — freshest activity first. Each card shows a status dot, the session name, which project and tool it belongs to, its running cost, and when it was last active. The status dot is the important part: it tells you whether the agent is working, waiting on your input, blocked, errored, or done, without you having to open the session.
| Status | What it means |
|---|---|
| Working | The agent is actively doing something. The dot pulses. |
| Awaiting input | The agent finished its turn and is waiting for you to reply. |
| Blocked | The agent hit a gate — a scope boundary, a checkpoint, or a question it needs answered. |
| Error | Something failed and the agent could not continue. |
| Completed | The session is done. |
| Idle | No recent activity. |
Tip
A card can pick up extra hints — an amber tint and a CPU icon when a session has been pegging your processor, a context-health ring when the session’s context is scored, and a small "near limit" tag if that session’s provider printed a rate-limit warning.
The needs-attention queue
Above the fleet, Mission Control pins a needs-attention queue: just the sessions that are awaiting input, blocked, or errored — the ones that cannot make progress without you. They are ordered oldest waiter first, so the session that has been stuck the longest is at the top. When every session is happily working, the queue is empty and disappears.
Because the oldest waiter is the one most likely to have gone stale, there is a shortcut to jump straight to it: press Cmd+J on macOS or Ctrl+J elsewhere and Operon opens the session at the top of the queue. It is the fastest way to clear a backlog of waiting agents — answer one, jump to the next.
The Bus gate inbox
Sometimes an agent does not just stop — it asks you a specific question and waits for the answer before continuing. Operon calls these ask-human gates, and Mission Control surfaces them in the Bus gate inbox at the top of the page. Instead of a bare "blocked" dot, you see the actual question and, when the agent offered choices, buttons to pick from. Answer inline and the agent unblocks immediately; there is no need to open the session and hunt for where it stopped.
Note
A session with a pending question shows up in both places — as a blocked entry in the needs-attention queue and as a full question card in the gate inbox. The inbox is the richer view; the queue is the quick jump.
Handling a session that needs you
- 1
Scan the queue
Open Home and look at the needs-attention queue. If it is empty, every agent is working and there is nothing to do. If it has entries, they are ordered by who has waited longest.
- 2
Jump to the oldest waiter
Press Cmd+J (macOS) or Ctrl+J to open the session at the top of the queue, or click any entry to open that specific one.
- 3
Answer the question or unblock the work
If the agent asked a question, answer it right in the Bus gate inbox — pick a choice or type a reply. Otherwise open the session, read where it stopped, and give it the next instruction in the terminal.
- 4
Repeat until the queue is clear
Each answer moves that session out of the queue. Jump to the next oldest waiter and keep going until Mission Control shows a happily-working fleet.
The global task board
Mission Control also has a companion Tasks view — reached from the Tasks entry in the sidebar — that aggregates the task boards of every active session into one place. It is a four-column kanban (To Do, In Progress, Blocked, Done) spanning all your sessions, so you can see the whole in-flight workload at once rather than opening each session in turn.
- Drag a card between columns to change its status; the move syncs back to the owning session.
- Click a card to jump straight into the session that owns it.
- Filter by project when you want to narrow the board to one codebase.
Note
The global board is a view over the same task data each session already tracks — it does not create a separate to-do list. Tasks are extracted automatically from your conversations and from your tool’s own todo updates.