Muse Code vs Rovo Dev CLI

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.

Rovo Dev CLI

Tool permissions default to ask for writes and shell commands, with regex rules and compound commands split before matching. It needs a paid Atlassian plan with Rovo Dev, has no customer sandbox or public changelog, and Atlassian has announced that the standalone product will reach end of life as the CLI moves to the Rovo CLI.

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

Rovo Dev CLI

1. Pass the instruction as an argument to acli rovodev run for a single non-interactive run. No JSON output flag or exit codes are documented
2. Use acli rovodev serve <port> and stream /v3/stream_chat?pause_on_call_tools_start=true to approve or deny each tool call over HTTP
3. Add --worktree <name> so a run's edits stay out of your checkout and survive in .rovodev/worktrees/<name>
4. Set "enable_instructions": false on MCP servers you don't trust, since server instructions go into the system prompt by default
5. Check /usage before long runs. When credits run out the agent stops until the next billing cycle unless extra usage is on