Module targets 

Modules

agy

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):

claude

codex

copilot

cursor

droid

gemini

grok

opencode

qwen

Structs

HookInput

HookResponse

ParseError

Enums

GatedPolicy

How a harness’s hook handles a gated command — see HookFormat::gated_policy.

InstallOutcome

Constants

UNKNOWN_WORKDIR

The working directory nothing can be inside: a relative path resolved against it lands outside every workspace, so a command whose safety rests on where its relative paths point is not approved, while one that names no such path classifies as it would anywhere.

Traits

HookFormat

Target

Functions

allow_reason

detect_installed

evaluation_dirs

The (cwd, root) a command is classified under. Most harnesses send no distinct project root, so the root defaults to the cwd, which engages the workspace boundary with the one directory known. Where the cwd is not the command’s own (HookFormat::cwd_is_the_commands), the reported cwd stays the workspace root and the command is placed at UNKNOWN_WORKDIR.

find

may_grant

May a GRANT be emitted for this command?

registry

respond

The decision for one parsed envelope: the response to emit, or None to abstain.