Install

Install MUON on macOS

MUON ships as a native macOS app (Apple silicon only) that hosts its own local backend and background runner — there is nothing else to start. The v1 build is unsigned, so the first launch requires one extra step past macOS Gatekeeper. That is expected, not a defect: see why it's unsigned below.

Requirements

• macOS on Apple silicon (arm64). Intel/universal builds are a follow-up, not available in v1.
• git installed and on your PATH. MUON operates on git repositories/workspaces and shells out to git for workspace identity, diffs, and merges.
• At least one coding-agent CLI installed and logged in. MUON drives your own agents; it never ships or authenticates one for you. Pick at least one:

Get the app

Download the app from getmuon.com/download: grab MUON-<version>-arm64.dmg, open it, and drag MUON into Applications. Every artifact ships with a published SHA-256 checksum (SHA256SUMS, served alongside the download) so you can verify what you got before you open it.

First launch: getting past Gatekeeper

Because the v1 build carries no Developer ID signature, macOS blocks the very first launch and calls MUON an app from an “unidentified developer.” You only do this once — macOS remembers your choice after.

1. Right-click → Open

   In Finder, Control-click (or right-click) MUON.app and choose Open, then confirm Open in the dialog that appears. A plain double-click only offers “Move to Trash” on an unsigned app — you must use right-click → Open.

2. Or: System Settings → Privacy & Security

   On newer macOS, after a blocked double-click, open System Settings → Privacy & Security, scroll to the “MUON was blocked” notice, and click Open Anyway.

3. Or: clear the quarantine flag from the Terminal

   The two options above are the documented path. If you'd rather do it from a terminal, the quarantine attribute macOS attaches to anything downloaded from the web can be stripped directly with:

   xattr -dr com.apple.quarantine /Applications/MUON.app

   This is the standard macOS mechanism for an unsigned app you trust — it does the same thing as clicking “Open Anyway,” just from the shell. Run it once, after the app is in /Applications.

Install the CLI and TUI

The terminal surfaces install with one command (requires Node 20+ and npm on your PATH):

curl -fsSL https://getmuon.com/install.sh | bash

That installs two commands: muon (the CLI — it auto-starts the local brain on first use, so there is no server to run) and muon-tui (the full-screen terminal cockpit). To register MUON as an MCP server with your own coding agent — so Claude Code or Codex can drive a governed crew from inside its own session — run muon mcp install afterwards. See the CLI reference and the MCP guide.

“Unsigned”, why, and is it safe?

MUON's v1 build is not signed with an Apple Developer ID certificate and is not notarized. Treat it as a controlled build, not (yet) a certificate-verified one.

• Why: Developer ID signing requires an active Apple Developer Program membership; wiring it in is deliberately staged as an off-by-default toggle so it can flip on later with a cert and no rework — the entitlements, the notarization hook (afterSign), and the config seam already exist in the build.
• What it means for you: macOS quarantines and warns on first launch, which is the friction above. There is no other behavioral difference — MUON still runs entirely on your machine.
• How to trust the build: every release ships with a published SHA256SUMS file next to the download — verify the DMG's checksum before opening it.

Auto-update

MUON makes no outbound network calls on its own, with exactly one opt-in exception: an update check against MUON's release feed (download.getmuon.com), toggled from the sidebar's Updates panel (off by default).

Where MUON stores data

Uninstalling: delete MUON.app. A published Homebrew cask's zap stanza will also clear the data directory; there is no cask published yet, so today that is a manual step.