Run a mission
Use when one goal needs planning first, several pull requests, or another agent to check the work, and you want to say it once.
A mission is one goal carried by a lead agent, the Conductor: it plans with you, starts the agents, another model checks each part, and only decisions come to you. The map shows that, with the one node that waits on you.
- Say the goal to an agent in a hide pane. For complex work the agent asks one line:
Shall I run this as a mission, or do it directly?It asks when the work needs planning or review first, two or more pull requests, another agent checking, or a long conversation. - Answer in words:
mission, ordirectly. You can also call it yourself: type/hide-missionin Claude Code or$hide-missionin Codex. - Plan with the Conductor in the same conversation. Say what done means, and whether the agents stop at ready pull requests (
Up to ready PRs) or go through the merge (Through the merge). Defaults live in Settings, under Mission. - Open the map. Press the
Missionchip on the Conductor’s pane, or the sidebar’sMissionsrow. TheMissionsscreen groups missions asYour turn,In progress,Waiting to mergeandFinished. The command palette entry isOpen missionsand has no shortcut until you bind one. - Work on something else. When a node waits on you, the mission moves into
Your turn, and its row or card shows the action:Answer,Read letters,See what's stuck,Take a look,MergeorJoin. - Answer a decision. The card names the node and says
awaiting decision. Press an option to mark it (the Conductor may mark oneRecommended), then pressAnswerto send it. Or pressWrite an answer…, type, and pressEnter. You can also answer in the Conductor’s conversation. - To change course, say it to the Conductor: “stop”, “resume”, “drop node 3”, “do this one first”. The map is for looking, not editing.
- To end it early, open
Mission menuon the map, chooseEnd mission…, thenAsk to end.Keep itbacks out.
Paste to your agent
Section titled “Paste to your agent”Run this as a mission: <the goal in one sentence>.Plan it with me first and show me the plan before you start any agent.Stop at ready pull requests; do not merge. Another model should check each part.Come back to me only for decisions.What you will see
Section titled “What you will see”- Each node is a card: its state (
Waiting,In progress,Done,Dropped) and, on its bottom line, its pull request for a code node, its preset (Research,Verify,Deploy,General) and then its result for a general node, or the outside pull request aWatchingnode waits on. - A
Deploynode asks you before it starts: its card turns yellow with what to look at once the work before it is done, and its worker starts after you say go. - A node that waits on you has a thick border and
Your turn. - At the end the Conductor writes a report. The mission closes as
Finished, or sits inWaiting to mergewhile a pull request is not in main yet. It moves toFinishedonce each is merged. - A cancelled mission does not reopen.
If it goes wrong
Section titled “If it goes wrong”- The row says
No Conductor. The lead agent’s session is gone. PressResume commandon the row to take it over. Answersays it could not send. The card shows why, such asNot sent · no Conductor. Resume the Conductor, then pressSend again.- A device does not answer. The map keeps its last values dimmed, and
Resume commandis disabled until the device answers.
Read more
Section titled “Read more”- Missions explains the map, the Missions screen and the settings.
- Tasks and status explains the rows and marks the map reuses.
- Previous guide: Answer only what needs you.