Antigravity transport
Antigravity has no SDK — AgentDock drives it as a real terminal process via node-pty and classifies its raw output.
The Antigravity adapter (src/main/agents/antigravity) is structurally different from the Claude Code and Codex adapters: there is no official SDK to integrate against, so AgentDock runs agy as a genuine PTY process and classifies what it prints.
Launch and permission flags
Permission mode is passed as a launch flag rather than switched live: --mode accept-edits, --mode plan, or --dangerously-skip-permissions for bypass; the default mode passes no flag at all. This is fixed for the life of the process, the same constraint Codex has for a different reason.
Output classification
AntigravityClassifier and AntigravityEventMapper pattern-match the raw terminal stream for permission prompts, authentication prompts, menus, and capacity errors, then translate recognized patterns into the shared agent event model. AntigravityStructuredEventMapper and AntigravityStructuredTransport handle a more structured headless-continuation path where available.
Note
Because this integration reads terminal text rather than a typed protocol, it's inherently more sensitive to changes in Antigravity's own CLI output than the SDK-backed adapters are — an unrecognized prompt string can stall a task rather than being classified correctly.
Model normalization
antigravity-model-normalization.ts and antigravity-model-catalog-service.ts reconcile Antigravity's own model/effort naming into the shapes the rest of AgentDock expects.