Skip to main content
뉴스로 돌아가기
뉴스

Mission Control: Know Which Agent Needs You

A right-edge panel that groups every agent by state and shows the pending question for anything waiting on you — no more hunting the canvas for a stuck agent.

Run five or six agents on a canvas and a new problem shows up: the canvas tells you where each agent is, not what it needs. One tile is three screens off to the left waiting on a permission prompt. Another finished ten minutes ago and you haven't noticed. Triage means panning around and clicking into tiles one at a time. Fleet — the Mission Control panel — fixes that by showing every agent grouped by state instead of by position, with the actual pending question visible right in the panel.

What you can do now

  • See every agent grouped by state — needs input, working, done, failed, idle, and exited — in a fixed triage order, so the agent that's been waiting on you is always at the top.
  • Read the pending question without leaving the panel — for any agent waiting on input, Mission Control shows the last couple of lines of its terminal, which is almost always the actual yes/no or permission prompt it's asking.
  • Jump straight to a stuck agent — click any row and the canvas flies to that tile, no hunting across a dozen tiles.
  • Watch Claude Code Dynamic Workflows progress per tile — if a tile is running a workflow with several subagents, Mission Control shows a line like Review 3/5 so you can see how far along it is without opening the tile.
  • Glance at the collapsed badge for a single number — the count of agents that need your input right now, the one number worth interrupting for.

How to try it

  1. Open a canvas with a few agent tiles running.
  2. The Mission Control panel appears automatically at the right edge once there's something to show.
  3. Collapsed, it shows a small pill badge with the count of agents needing input. Expand it to see the full list grouped by state.
  4. Click any row to fly the viewport straight to that tile.

Why it matters / use case

Once you're past two or three agents, the canvas stops answering the question that matters: "who's blocked on me right now?" That answer has nothing to do with where a tile sits on the canvas — it's about state. Mission Control answers it directly. Instead of holding six tiles' worth of state in your head and scanning the canvas to find the one that's stuck, you read a single ordered list and decide whether the pending prompt is worth interrupting what you're doing — often without ever leaving the panel.

What's next / limitations

A plain shell tile never appears in Mission Control — only tiles recognized as agent CLIs do. The panel shares its right-edge slot with the Flows/Exploration/Team Hub drawer, so the two can't be open at the same time; opening one collapses the other.