Antigravity CLI vs Mirror CLI

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.

Mirror CLI

Mirror CLI is Apache-2.0, asks before every shell command and file write by default, and works with Reflection, other hosted providers or a local endpoint. It is a one-day-old 0.1.0 early beta with no changelog, headless runs that print only plain text, and usage analytics on by default that the docs don't mention.

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

Mirror CLI

1. Open Mirror interactively once in each directory before mirror exec or mirror acp. Both refuse to run until the usage and folder notices are accepted
2. Pass --approval-mode auto to mirror exec only inside a container or VM. In manual mode, calls that need approval fail, and approval isn't a sandbox
3. Set --max-iterations on unattended runs. Turns are unlimited by default
4. Check the result with your own tests. exec returns 0 whenever it prints an answer
5. Never share logs recorded with --log-level debug. The docs say they contain request headers with the API key