Antigravity CLI vs Droid 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.

Droid CLI

droid exec is read-only unless --auto raises the autonomy level, with command rules, an optional kernel-enforced sandbox, JSON output and documented exit codes. No free tier, status page or security.txt was found, the source is closed, and usage metrics go to Factory by default.

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

Droid CLI

1. Set FACTORY_API_KEY (starts fk-) from the API keys page in Factory settings for headless runs. Interactive use signs in through a browser
2. Start with droid exec and no flags for analysis. Add --auto low for edits and --auto medium for installs, tests and local commits
3. Use --output-format json and read is_error, num_turns and session_id. Treat a non-zero exit code as failure
4. Set sandbox.enabled to true before running on untrusted code. In droid exec a sandbox violation is denied without a prompt
5. Pin the version in CI with npm install -g droid@<version>, or set FACTORY_DROID_AUTO_UPDATE_ENABLED=false on standalone installs, which update themselves