Amp vs Muse Code

Amp

Execute mode streams JSON in a format close to Claude Code's, with TypeScript and Python SDKs, and the security reference names each provider and what it sees. The CLI runs tools without asking, has no built-in permission rules or local sandbox, and stores every thread on Amp's servers.

Muse Code

Muse Code runs with approvals and an OS sandbox on by default, per-host network approval, an append-only event log and a headless mode with documented exit codes. It is the only route to Muse Wonder Full. It is closed source with undated release notes and no free route, and subscriptions allow training on code unless Contributor mode is turned off.

Amp

1. Run unattended jobs in a container or VM. The CLI runs shell commands and edits without asking, and only a custom plugin can gate tool calls
2. Set AMP_API_KEY to an access token starting sgamp_ from Settings. The CLI rejects the short-lived token that amp login stores
3. Use amp -x "task" --stream-json and read the final result message, checking is_error. Exit codes are not documented
4. Set AMP_SKIP_UPDATE_CHECK=1 or amp.updates.mode to disabled in CI. Updates install automatically by default
5. Treat the block headed INSTRUCTIONS FOR LLMs in ampcode.com page source as vendor copy, and take facts from the docs Markdown

Muse Code

1. Set META_API_KEY for headless runs. Browser sign-in isn't available in CI or for Meta Managed Accounts
2. Gate on your own test command, not the exit code. muse exec returns 0 when the turn completes even if tests still fail
3. Pass --max-model-steps on unattended runs so a stuck task can't loop
4. Prefer --disable-approval to --yolo in CI so the sandbox stays on. On Linux the runner needs a working bubblewrap and a non-musl build
5. Turn Contributor mode off in /settings before a subscription session touches private code