Mission Control Handoff
Purpose
Present the Mission Control handoff as a clean, evidence-aware final summary.
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 orchestration is complete or near complete.
- The user asks for the handoff or final report.
- You need to verify what changed and what evidence backs it.
Workflow
- Call
mission_control_get_handoff or mission_control_get_handoff_summary.
- Read the handoff resource for status, evidence level, and limitations.
- Summarize what changed, how to run, validation or evidence, important files, and next tasks.
- Warn explicitly if the run was dry-run, incomplete, or weakly evidenced.
Mission Control calls
Tools:
mission_control_get_handoffmission_control_get_handoff_summary
Resources:
mission-control://projects/{project_id}/handoffmission-control://projects/{project_id}/status
User-facing output
- Show status, confidence or evidence level, what changed, how to run, validation or evidence, known limitations, recommended next tasks, and important files or artifacts.
- Warn if tests were not run, evidence is missing, the handoff is incomplete, or the run was dry-run.
Approval behavior
If the handoff requires explicit review or sign-off, relay that approval instead of declaring the work accepted.
Never do
- Do not present a partial report as finished.
- Do not suppress missing evidence.
- Do not claim Codex performed the work directly.
Failure and fallback
If no handoff exists yet, say so directly, provide the current status, and point the user to the blocking approvals or remaining tasks.
Example invocation
Get the Mission Control handoff and summarize what changed.
1---2name: mission-control-handoff3description: Retrieve and present the final Mission Control handoff. Use when the user asks for the finished result, final summary, what changed, how to run it, evidence, limitations, or next tasks.4---56# Mission Control Handoff78## Purpose910Present the Mission Control handoff as a clean, evidence-aware final summary.1112The Codex chat agent is not the Mission Control Manager. It is the bridge between the user and the Mission Control Manager.1314## Use when1516- The orchestration is complete or near complete.17- The user asks for the handoff or final report.18- You need to verify what changed and what evidence backs it.1920## Workflow21221. Call `mission_control_get_handoff` or `mission_control_get_handoff_summary`.232. Read the handoff resource for status, evidence level, and limitations.243. Summarize what changed, how to run, validation or evidence, important files, and next tasks.254. Warn explicitly if the run was dry-run, incomplete, or weakly evidenced.2627## Mission Control calls2829Tools:30- `mission_control_get_handoff`31- `mission_control_get_handoff_summary`3233Resources:34- `mission-control://projects/{project_id}/handoff`35- `mission-control://projects/{project_id}/status`3637## User-facing output3839- Show status, confidence or evidence level, what changed, how to run, validation or evidence, known limitations, recommended next tasks, and important files or artifacts.40- Warn if tests were not run, evidence is missing, the handoff is incomplete, or the run was dry-run.4142## Approval behavior4344If the handoff requires explicit review or sign-off, relay that approval instead of declaring the work accepted.4546## Never do4748- Do not present a partial report as finished.49- Do not suppress missing evidence.50- Do not claim Codex performed the work directly.5152## Failure and fallback5354If no handoff exists yet, say so directly, provide the current status, and point the user to the blocking approvals or remaining tasks.5556## Example invocation5758`Get the Mission Control handoff and summarize what changed.`
MN755