Operator workspace
Many missions stay legible
Running one agent is a conversation. Running six crews across four repositories is an operations problem. The workspace exists so that a person can hold that many moving parts without a spreadsheet, and it is derived from the runtime rather than maintained by hand.
Attention board
The landing view sorts itself
Each card compresses the task, the agents, the branch, the session, the checks, the pull request, the review, the budget, the memory conflicts and the next action. Nothing on it is a status somebody has to remember to update.
- Idempotency keys on the charge pathmuon/idempotency-keysCrew
Codex, Cursor, OpenCode
StateMerge gate open
NextYour decision
- Move the webhook worker off the legacy queuemuon/webhook-queueCrew
Claude Code, Codex
StateChecks running
NextNo action needed
- Backfill the customer search indexmuon/search-backfillCrew
Codex
StateTwo memories contradict
NextRead the conflict
- Drop the unused billing columnsmuon/billing-cleanupCrew
Cursor
StateWaiting on a budget increase
NextApprove or decline
Styling follows the facts. A card is amber because two memories genuinely contradict each other, not because someone dragged it into a column called At risk.
Mission workspace
One mission, everything about it in one place
Selecting a card opens a single workspace with the terminal and chat, the diff, the checks, the reviews, the brain, the graph, a browser preview, the budget and the lineage of the run.
- Watch the live agent panes as they work, or read the beat log after the fact
- Open any claim in the diff and see the decisions recorded about that symbol
- See the budget spent per lane and per turn, in tokens and in money
- Replay the whole run from the authoritative record, including the runs that failed
- Every gate names what it is protecting and what recovery would clear it
The queue of things only you can do
Merges, releases, budget increases, permission changes, secret access and memory confirmations collect in one queue with the evidence attached. You are not hunting through terminals for the thing that is blocked.
When nothing needs you, the queue is empty and the crew keeps working inside the authority you already granted.
Surfaces
Four clients, one brain
The runtime owns the processes and the sessions. Every interface is a client of it, so nothing you do in one surface is invisible in another.
The app most people live in
Attention board, mission workspace, native agent panes, diff, checks, reviews, gates, memory and graphs in one window. It attaches to the session supervisor rather than owning the processes itself.
A harness of harnesses
The terminal client is dense, keyboard first and built for people who never leave the shell. It attaches to the same live sessions, so you can start a mission on the desktop and finish it in a terminal.
Scriptable and honest about state
Start missions, inspect runs, read the ledger and drive checks from a script or a CI job. Every command reports the same state the interfaces show, because it reads the same record.
The brain as a tool for your agents
An MCP server exposes retrieval, impact and decision history to any agent that speaks the protocol, including agents running outside a MUON mission.