ccc-mission-controllisted

# $ccc-mission-control — Mission Control One board that answers "**who's working on what?**" without reading a single log line. Every CC Commander session already journals its agent runs, tasks, and delegations to `~/.claude/commander/` (`subagent-runs.jsonl`, `agent-runs.jsonl`, `tasks.jsonl`, `mission-control/events.jsonl`). Mission control turns those logs into a picture a non-coder can read: agent roster, task board, delegation flow, and a plain-English summary. > 🔒 Privacy: everything runs locally by default — the live dashboard binds to 127.0.0.1 and no data leaves your machine. The one exception is the optional 📤 snapshot artifact: publishing uploads the snapshot (agent names, task subjects, timings) to your private claude.ai artifact URL — it starts private to your account, but treat it as leaving the machine. The skill always asks before publishing, and never publishes automatically. ## How it routes On `$ccc-mission-control` with no argument, open a click-first picker: ``` AskUserQuestion: question: "Mission control — how do you want to see your agents?" options: - 🖥️ Open live dashboard — auto-refreshing panel that sits beside your chat - 🛰️ Publish snapshot artifact — a living status page you can keep or share - 🗣️ Plain-English status — narrate it right here, zero jargon - 💡 Review & promote suggestions — triage the ideas agents have surfaced - ⏹️ Stop dashboard — shut the local server down ``` Explicit sub-commands skip the pi