Google Antigravity
How AgentDock detects, launches, and integrates with Google Antigravity.
Google Antigravity is one of the three coding-agent CLIs AgentDock can drive. You install and authenticate it yourself — AgentDock only detects and launches whatever is already working on your system.
Prerequisites
- Antigravity installed and authenticated, per Google's own instructions.
- No AgentDock-specific setup beyond that — see Getting started: connecting your agents.
How AgentDock detects it
AgentDock probes for agy first — this is the confirmed, verified command name. It also probes for antigravity and google-antigravity as fallbacks, but those two are unverified naming guesses rather than confirmed alternate binaries. If agy is on your PATH (plus a few known install locations on Windows and macOS), AgentDock will find it. Linux detection is PATH-only.
You can override the detected path in Settings → Agents, which runs a live "Test" action and shows diagnostics.
How the integration works
Unlike Claude Code and Codex, Antigravity has no official SDK integration in AgentDock. Instead, AgentDock runs it as a real terminal process via node-pty and classifies the raw terminal output — permission prompts, authentication prompts, menus, capacity errors — by pattern-matching the text it prints, rather than reading a structured event stream.
Note
Because this integration reads terminal text rather than a structured API, its behavior can be more sensitive to changes in Antigravity's own CLI output than the Claude Code and Codex integrations are.
Permission mode is controlled via the --mode flag at launch: default, accept-edits (--mode accept-edits), plan (--mode plan), and bypass (--dangerously-skip-permissions). See Permissions for details.