mission-control-subagent-burstlisted

# Mission Control Subagent Burst ## Purpose Route short-lived Codex subagent burst recommendations through Mission Control. The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager. ## Use when - The task is read-heavy and parallelizable. - The user wants bounded parallel exploration or review. - Mission Control should recommend whether a burst is worth it. ## Workflow 1. Check status and current orchestration context. 2. Fetch subagent policy. 3. Ask Mission Control to recommend a burst for the current task. 4. If a pending decision is created, render it in Codex chat and wait for the user. 5. After approval, fetch the batch and present spawn instructions or manual prompt text. 6. When results come back, send them to Mission Control result ingestion. ## Mission Control calls Tools: - `mission_control_get_status` Daemon/API: - `GET /api/subagent-policy` - `POST /api/projects/{project_id}/subagent-bursts/recommend` - `GET /api/projects/{project_id}/subagent-batches` - `GET /api/subagents/batches/{batch_id}` - `POST /api/subagents/batches/{batch_id}/results` - `GET /api/decisions/{decision_id}/bridge-message` - `POST /api/decisions/{decision_id}/answer` Resources: - `mission-control://projects/{project_id}/status` - `mission-control://projects/{project_id}/pending-decisions` ## User-facing output - Explain whether Mission Control recommends a burst. - Show purpose, count, risk, and the proposed subag