Product
Three parts that only work together
A runtime without a brain is a process manager. A brain without a runtime is a memory API. A dashboard over neither is decoration. MUON ships the runtime, the brain and the operator workspace as one product, and the value comes from the seams between them.
Runtime plane
It runs the agents you already installed
MUON owns the processes, the terminals, the sessions and the worktrees. Every agent gets a universal control floor as soon as it can host a bounded control plane, and richer abilities are unlocked by proving them rather than by being on a list.
- A shared session supervisor owns every terminal, so the desktop app and the terminal client attach to the same live run
- Sessions survive a restart. A crashed agent resumes with its context, its claim and its history intact
- Each writing agent gets its own git worktree, so two agents never fight over the same checkout
- Structured sessions use the Agent Client Protocol wherever the agent supports it, with native drivers kept only where they add something real
- Authority never branches on a vendor name, and registering an agent grants it nothing by itself
Every vendor can coordinate or work
No coding agent is excluded from the coordinator path or the worker path. An agent may coordinate as soon as it can host the control plane. It may write, steer, resume, fork, review or spawn governed children only after each of those abilities is proven against a vendor neutral contract.
See what each agent can do todayTruth plane
One brain holds what the project knows
The relational ledger is the authority. The graphs are rebuildable views over it, which means a corrupted index is an inconvenience rather than a lost history. Every claim carries who wrote it, what supported it, who confirmed it and what it replaced.
What calls what
Symbols, calls, data boundaries, impact and code taint, built from your repository. It answers the question an agent should ask before an edit: who breaks if this changes.
What the team decided
Memories, decisions, constraints, provenance, contradictions, confirmations and supersession. It answers who decided what, and why, long after the conversation is over.
Who is doing what now
Live agents, tasks, sessions, work claims, messages between agents, context frames, handoffs and attention state. It is what stops two lanes from quietly doing the same job.
Context
Context is a budget that MUON spends carefully on every call
Cheap tools paste the top few search hits in front of the prompt. MUON treats the window as a portfolio and allocates a bounded share to each kind of information, adapting to the role, the phase of the mission and the risk of the change.
Context allocated for one turn
200,000 TOKEN WINDOW · IMPLEMENTER ROLE
- Authority and role contract8%
- Mission and task brief12%
- Standing canon14%
- Task relevant memory18%
- Code and decision evidence22%
- Live coordination state9%
- Conversation continuity7%
- Response headroom10%
The shares move with the role, the phase of the mission, the risk of the change and how much the crew already knows. Every turn records what was eligible, what was included, what was left out and the reason for each.
Operator plane
You command and decide, you never guess
The operator surface renders status from the runtime and the ledger. It cannot invent a state. When it says checks are green, a check ran, and you can open the evidence behind it.
- 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