Antigravity CLI vs Muse Code

Antigravity CLI

Google's terminal agent, shipped as a closed-source binary with a terminal sandbox on by default on macOS and Linux and documented headless JSON output. Interactions are used to improve Google products unless users opt out, and a headless run exits 0 when a tool is denied.

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.

Antigravity CLI

1. Read the status field from --output-format json and read stderr too. A tool refused for lack of approval still exits 0
2. Pre-approve each shell command and tool a headless run needs with action(target) rules under permissions.allow in ~/.gemini/antigravity-cli/settings.json, because headless runs cannot ask
3. Export GEMINI_API_KEY after setting modelProvider to gemini. The CLI won't start when the key is missing, and setting the variable alone has no effect
4. Turn off Enable Telemetry in the Account settings before running on private repositories if Interactions should not be used for product improvement
5. Set --print-timeout explicitly. The docs give a five-minute default, while agy --help shows 0s

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