The muon CLI

Talk to the super-orchestrator like you'd talk to Claude: it plans, dispatches the fleet, and reports — gates stay yours. With no --message, opens an interactive REPL (/quit to exit). With one, sends it and exits (scriptable).

One job's status plus its crew budget (with --job-id), or the list of active jobs (optionally filtered to one chat).

The crew's kill switch — interrupt one running job.

Send a steer message to a running dispatched job.

Raise a mission's descendant wall-clock time pool — the operator's recourse when a crew exhausts its budget. Targets the root orchestrator job; delegated children share its pool.

Discovery table: name, vendor handle, stable id, readiness — then the exact next command for the first actionable row.

Current fleet counts per vendor and each agent's live status.

Resize the fleet per vendor, 0–3 instances each. A resize never kills a working agent. At least one --<vendor> flag is required.

List fleet agent instances with live status.

Add a note. --kind is one of decision, constraint, convention, attempt, question. Optional anchors: --task-id, --lane-id, --module, --symbol (<module>#<name>), --topic.

Lexical search over notes in the fenced workspace.

Browse the governed memory library: filter by status (all/active/paused/rejected), confirmation state, kind, trust, or free text.

Recall notes by task, lane, module, or topic.

The review queue: notes still unvouched and awaiting a human confirm or reject. A MUON-vouched or operator-confirmed note is settled and never listed here.

Operator-only governance acts — mark a note human-confirmed, or reject it (kept for traceability, hidden from recall).

Team memory sync over plain files — no MUON cloud. Export writes this workspace's confirmed notes as a content-addressed pack; import stages a teammate's pack as unconfirmed proposals in your review queue; sync does both. Operator-tier only.

Register MUON's MCP server with your own CLI's config. See the MCP page for what it does and does not grant.

Explain the tier a hand-started session would get, and every reason it could be wrong — brain state, token source, whether the recorded muon-mcp path still resolves, per-vendor registration.

Remove exactly the entry MUON wrote; every other server and key in that config file is left untouched.

Mint (or revoke) a governed dispatch seat for a coordinator CLI you run yourself — Claude Code and Codex only, the two lanes that can hold the coordinator seat.

Backend connectivity and lane health: the versioned capability preflight contract MUON's own surfaces read from. Never rejects — every unreadable source degrades to an honest “unknown” with a reason.

App version, the indexed code-graph commit, the workspace's actual HEAD, and whether the two disagree (a stale index).

Guided first run: per-vendor installed/authenticated readiness plus the exact fix for any gap.

Seed and dispatch a tiny, safe, additive sample task so you can watch the whole loop run without inventing one yourself.

The pre-edit gate for the terminal: blast-radius fused with governed memory, prior decisions, live cross-agent activity, and pending proposals for a symbol or file.

The approval queue from the terminal, including review's exact artifact digest and REVIEW BLIND file list for merge gates.

Stop the persistent local brain and runner that CLI commands auto-start. The desktop app stops its own processes on quit; this is the CLI's off switch for the pair it spawned.