MUONMUON

How it works

One mission in. One reviewed result out.

Your team gives MUON the outcome. MUON proposes the crew, launches bounded workers, keeps their context aligned, and brings the final result back with the evidence needed to decide.

Explore the product →
  1. 01

    Connect

    Confirm the crew is ready

    muon onboard

    MUON checks whether the supported provider CLIs are installed and authenticated, then gives a concrete next step for every gap.

  2. 02

    Plan

    Give MUON one mission

    muon workflow run review-first "Harden the merge path"

    MUON turns the request into explicit jobs, roles, lane suggestions, ownership boundaries, approval points, and a clear handoff order.

  3. 03

    Assign

    Launch governed workers

    muon workflow apply --run-id <run-id>

    MUON creates bounded Claude Code or Codex jobs with lineage, workspace limits, budgets, and cancellation controls, then records their progress against the mission.

  4. 04

    Coordinate

    Keep the crew in sync

    muon approve review --approval-id <approval-id>

    Relevant memory, peer activity, structured handoffs, checks, and conflicts move forward with the work instead of relying on a human to relay them.

  5. 05

    Review

    Decide what can merge

    muon ship --task-id <task-id> --lane codex

    MUON presents the checks, changed files, approval history, second-opinion evidence, and exact worktree result before a person makes the merge decision.

The division of responsibility

MUON handles coordination. People set direction, approve consequential actions, and decide what ships.

Human control

One connected record

The mission stays understandable from start to finish.

01

Intent, task, lane, scope, and ownership

02

Provider readiness and execution identity

03

Confirmed memory, provenance, and peer context

04

Events, handoffs, checks, decisions, and bound artifacts