Integrations

MUON runs the agents while you keep the accounts and the billing

MUON drives the agent binaries already installed on your machine and signs in with nothing. Your Claude subscription stays yours, your Codex usage bills to your own account, and no vendor token is ever stored by us. Adding an agent to a crew does not add a bill.

Supported agents

What each agent tends to do well

Roles are not tied to vendors. Any capable agent can take any lane it has proven it can hold. In practice, teams settle into patterns like these.

Claude Code

Coordinate, write, review

Strong at holding a long mission together and at explaining why it chose an approach. Often runs as the coordinator.

Codex

Coordinate, write, review

Fast and precise on well scoped implementation work. Usually holds the write claim on the files a mission changes.

Cursor

Explore, review

Good at tracing a behaviour across a repository. Frequently the lane that finds the caller nobody remembered.

OpenCode

Explore, review

Public code and easy to point at a review role, which keeps review independent from the model that wrote the code.

Any ACP agent

Universal control floor

Any agent that can host MUON's bounded control plane can join a crew. Richer abilities unlock as the agent proves them.

Conformance

An agent earns each capability instead of being trusted with it up front

Registering an agent grants it nothing. Each level of authority is unlocked by proving the matching capability against a contract that does not mention any vendor name.

Terminal and session controlEvery registered agent
Structured sessions over ACPAgents that implement the protocol
Write authority and file claimsProven write conformance
Steer, pause, resume and forkProven lifecycle conformance
Governed child agentsProven child broker conformance
Review with evidence obligationsProven review conformance

Beyond agents

Other tools can read the same brain through the MCP server

Everything MUON knows about a repository can be read by tools outside a mission, under the same scoping rules.

MCP server

Retrieval, impact analysis and decisions are exposed as tools

Any agent that speaks the Model Context Protocol can query the brain for relevant memory, the blast radius of a symbol and the decision history behind a file.

Read the MCP documentation
Git

MUON works through worktrees, branches and pull requests

Each writing agent gets its own worktree, so parallel work never shares a checkout. Branches and pull requests follow the conventions your repository already uses.

Licence

Public source, with one reserved use

MUON's source is public under PolyForm Noncommercial 1.0.0 plus an Individual Use Grant, so one person can read it, build it and run it free, including at work. Linking instances across people is licensed separately.

Read the licences