Update and uninstall

muon update              # update the CLI/TUI/MCP and the desktop app
muon update --check      # installs nothing; only records the verified release pointer
muon update --dry-run    # print what would run instead of running it
muon update --cli-only   # update only the CLI/TUI/MCP half
muon update --desktop-only  # update only the desktop app half (macOS)
muon update --host <url>    # read releases from a specific host

• --cli-only and --desktop-only exclude each other — pass one or neither.
• On a non-macOS host, --desktop-only reports there is nothing to update rather than doing nothing silently.
• After an update, agent sessions that are already open keep the previous MUON tools until they reconnect: run /mcp in Claude Code, or restart your Codex, Cursor, Kiro or OpenCode session.

MUON authenticates the signed release metadata and verifies downloaded artifacts against it. The CLI installer also checks package identity, shrinkwrap and dependency contents. It refuses a mismatch.

The CLI installer retains the previous installation while validating the new one. If validation fails, it attempts to restore the previous link and reports any rollback failure. The desktop updater stages a replacement app before swapping it into place. These recovery paths do not bypass the signed release's version floor.

• A record of the newest signed release this Mac accepted is kept at ~/.muon/release/channel-state.json. It enforces a version floor: MUON will not accept a release older than the one installed. See Troubleshooting → Corrupt release state if that record is reported corrupt.
• The release signing keys and the exact verification commands are on the release signing keys page.

In the app, Settings → Updates checks MUON's release feed when you click Check for updates. Checking on every launch is a setting, and it is off by default — turn it on in Settings if you want it.

An unmanaged app installed in /Applications applies the update after you choose to download and apply it: it verifies against the feed, swaps the app in place and relaunches, keeping a rollback copy until the new version boots. A copy anywhere else can only tell you a newer release exists.

Earlier CLIs used npm-global packages such as muon-cli, @muon/cli and @getmuon/cli. If MUON finds the CLI there, the first muon update moves it into MUON's own verified install under ~/.muon/cli — a one-time step it announces as it does it. muon update --check tells you when this move is pending without performing it.

muon uninstall runs npm-global uninstall for muon-cli, @muon/cli and @getmuon/cli. It sends a stop signal to a detected live brain first and preserves the data directory. Quit the desktop app and run muon shutdown before uninstalling so the brain and runner can stop cleanly.

muon uninstall        # prompts for confirmation at a terminal
muon uninstall --yes  # the explicit, scriptable path

If npm removed nothing — MUON was installed another way — remove the muon and muon-tui binaries from your PATH by hand.