Crush vs Muse Code

Crush

Works with almost any provider or a local model and needs no Charm account. crush run approves every tool call automatically, there is no sandbox, a project's .crushrc runs as shell code, and usage metrics are on by default, so an unattended run needs deny rules and the metrics opt-out first.

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.

Crush

1. Add permissions deny rules or a PreToolUse hook before crush run. It approves every permission request in its session
2. Read .crushrc, crushrc and crush.json in a cloned repository before running Crush there. They execute as shell code at startup
3. Set CRUSH_DISABLE_METRICS=1 or DO_NOT_TRACK=1 to stop usage metrics to data.charm.land
4. Wrap crush run in your own timeout. It has no turn, time or cost limit flag
5. Configure a provider by environment variable or crushrc first. With none, crush run exits with an error asking for interactive setup

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