FAQ
Questions people ask before they install it
If something here is unclear or your question is not covered, write to us and a person will answer.
Questions
The basics
What is MUON?
MUON is a runtime that runs your coding agents as a governed crew. You state an outcome, it plans a crew from the agents installed on your machine, gives each one a role and a scope, keeps a shared memory they all read, and stops for you at the decisions that matter. It is not a model and it is not another chat window.
Is MUON another coding agent?
No. It drives the agents you already use. Claude Code, Codex, Cursor and OpenCode keep doing what they are good at, and MUON handles the parts none of them own: coordination, shared memory, scope, gates and the record of what happened.
Why would I want more than one agent on a task?
Because a single agent reviewing its own work tends to approve it. A crew lets one model implement, a different model review, and a third explore the parts of the codebase nobody thought to check. The disagreement between them is where most of the value comes from.
Questions
Running it
What do I need installed?
At least one supported coding agent, signed in with your own account, plus git. MUON installs as a desktop app or from the command line and detects the agents already on your machine.
Do the agents fight over the same files?
No. Each writing agent gets its own git worktree and takes an exclusive claim on the files it is changing. Another lane that needs those files coordinates with the holder instead of editing around it.
How much control do I keep?
You approve the envelope, and inside it the crew works without interrupting you. Changes that reach sensitive paths, merges, releases, budget increases and memory confirmations are authorized by you — at the gate with the evidence attached, or through standing consent you grant per agent and can revoke at any time. Two things never ride on standing consent: egress, and a merge MUON cannot certify against the code graph — review-blind files need your eyes, every time. Every automatic approval is recorded as your decision.
Can I use it from the terminal?
Yes. The terminal client and the command line attach to the same live sessions as the desktop app, so you can start a mission in one and finish it in another.
Questions
Memory and trust
How does shared memory avoid becoming noise?
Agents can propose anything, but proposing is not the same as being believed. A claim passes deterministic checks, then needs independent corroboration from a second agent, and only a person or a scoped steward can make it company canon.
What happens when memory goes stale?
Memories are anchored to code. When the code they describe changes, the memory is marked as stale rather than served quietly, and the crew sees that the ground moved.
What if two confirmed memories contradict each other?
The mission raises the conflict instead of picking a side. Both claims and their sources land on your desk, and the resolution is recorded as a supersession so the history stays readable.
Questions
Privacy and cost
Does my source code leave my machine?
No. The runtime, the worktrees and the code graph are local. Teams share decisions and memory, not repositories.
Do you store my agent credentials?
No. Agents run under the credentials you already configured locally, and MUON holds no vendor tokens.
What does it cost?
It is free for one person. Teams pay $10 per named person each month for shared memory, coordination and the audit trail. Model usage is billed by your vendors at the rate you already pay.
Questions
The licence
Is MUON open source?
Not in the OSI sense, and we would rather say that plainly. The source is public at github.com/Sweetdevil144/muon under PolyForm Noncommercial 1.0.0 plus an Individual Use Grant: one person can read the code, build it, and run it free, including for work they do for an employer. Linked Operation — instances coordinating across people — is reserved and licensed separately. The licenses page and the grant in the repository are the controlling texts.
What is Linked Operation?
Two or more people's MUON instances sharing, syncing, or coordinating memory, code graphs, crews, claims, or findings — by any means, including something you host yourselves. One person on their own devices is Individual use and always free; the moment it becomes a shared brain across people, it is Linked Operation and needs a commercial licence.
Can my whole company use the free download?
Yes — each person, independently. Ten engineers can each install MUON on their own machines under the Individual Use Grant, employer laptops included. The organisation does not receive a licence by aggregation: what needs a licence is linking those instances together, not the number of people who happen to use MUON alone.