Antigravity CLI vs Crush

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.

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.

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

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