Antigravity CLI role (Reference implementer)
Structured workflow (v2.4 lineage) This reference follows the retained Plugin / source Legacy runtime and may include later fixes; it is not a frozen v2.4.0 snapshot. npm 3.x Web does not expose these structured APIs. Original v2.4.0 docs and migration · Current Web guide.
NOTE
This page describes Google Antigravity CLI's responsibilities in the default reference workflow. The underlying .agent-bus runtime is agent-agnostic and allows assigning the implementer role to other registered agents.
In the default reference workflow, Google Antigravity CLI (agy) fulfills the implementation role:
- claims an
IMPLEMENTorCHANGES_REQUESTEDmessage from.agent-bus/inbox/antigravity/new; - edits source code, tests, UI, and build configuration;
- performs browser, unit, or UI validation when required;
- runs the agreed checks and records evidence under
.agent-bus/evidence/; - creates a focused Git commit and reports
IMPLEMENTATION_DONE.
Antigravity does not approve its own work and does not merge, tag, push, deploy, or publish. It retains its native Google account authentication and model subscription.
The Plugin Task path uses the canonical Execution Session Runtime. task dispatch validates the resolved command, opens or reuses one Runtime-owned persistent PTY, and records the Task's non-owning sessionId. After CHANGES_REQUESTED, the next explicit dispatch reuses the same healthy Session and writes the feedback into that PTY context. A Session in exited or failed is reported as a fact and is never retried in a loop. The separate CLI launch command retains its legacy bus-supervised compatibility policy; it is not the Plugin Session Manager.
Session status, bounded output, input, and close are available through the Coordinate Agents MCP Session tools. They operate on the Runtime-owned process only and never type into or control the Codex App Terminal UI.
Use native agy directly. If it already has a global proxy configured, no project-specific proxy wrapper is needed. Clear any old wrapper prompt template when switching:
npx @hogancv/coordinate-agents@2.4.0 config set agent.antigravity.command agy
npx @hogancv/coordinate-agents@2.4.0 config set agent.antigravity.args '[]'The native CLI provides agy --continue to continue the most recent conversation and agy --conversation <id> to resume a conversation by ID. These options remain available when invoking agy directly with its existing global proxy configuration.
The project command, if explicitly present, takes precedence over ~/.coordinate-agents/config.json, which takes precedence over the Adapter default agy. launch and Session dispatch check the resolved executable before starting. Spawn failures, non-zero exits, and CLI conversation/runtime failures write structured ERROR/Session facts, preserve bounded output, and stop. They are not automatically retried. Login state is not preflighted; a login/provider error reported by agy is handled as a runtime failure with a bounded stdout/stderr tail.
Permission and sandbox arguments
Workspace settings support standard prompt mode or automatic approval. The adapter default is auto-approval via --dangerously-skip-permissions. In auto-approval mode, launches automatically approve tool permission requests, including file writes and command execution. The executable field remains agy (or its exact override); arguments are passed separately as an array, not shell text.
Explicit project arguments take precedence over user arguments, which take precedence over this default. An explicit args: [] opts out. Existing configured argument arrays are preserved and the flag is not duplicated. Running Sessions keep their original arguments; create a new task or explicitly restart to apply new settings. Custom Terminals use their separate Generic CLI configuration.
The one-shot launch appends --prompt-interactive <prompt>; a persistent Session uses --prompt-interactive= and delivers the first instruction through its PTY unless the configured template consumes {prompt}.
The published npm 2.4.0 runtime retains its original explicit-permission behavior. To enable automatic approval there, configure it explicitly:
npx @hogancv/coordinate-agents@2.4.0 config set agent.antigravity.args '["--dangerously-skip-permissions"]'doctor verifies the executable/version, not provider authentication or the permission state of an already running CLI.