Expand description
Antigravity CLI (agy) — Google’s successor to the retired Gemini CLI. Hooks are configured
via a hooks.json in the customization root (~/.gemini/config/ globally, .agents/ per
project). The run_command PreToolUse hook decision set is allow / deny / ask /
force_ask. Verified LIVE against v1.1.2 CLI on 2026-07-13 (see HARNESS-BEHAVIORS.md):
deny→ hard block, our reason shown to the model. WORKS.force_ask→ forces a human prompt, ignoring agy’s Always-Allow cache. WORKS.allow→ does NOT suppress agy’s ownrequest-reviewconfirmation in the CLI; the user is still prompted. So there is no effective grant on agy 1.1.2. We still emitallowfor a safe command: it is semantically correct, harmless (agy prompts anyway by default), and future-proof if a later build honors it.
agy’s default toolPermission=request-review prompts for run_command on silence, so it HAS
human review — a gated command therefore escalates (force_ask) rather than hard-denies. We use
force_ask over plain ask because ask respects the Always-Allow cache: a user who once
picked “always allow commands starting with cat” would have a gated cat /etc/hosts auto-run.
Antigravity FAILS CLOSED on a missing/malformed decision. See docs/design/harness-capability-model.md.