Antigravity

Jackalope runs the installed Antigravity CLI (agy), using its existing sign-in, model selection and permission settings. The adapter targets the streaming CLI contract verified with 1.1.26. The GUI application alone is not sufficient.

Setup and use

1. Install the CLI from Google's installation guide.
2. Run agy in a terminal and complete sign-in. Return to Jackalope and choose Agents → Check agents. Windows discovery checks PATH and %LOCALAPPDATA%/agy/bin; other systems also check ~/.local/bin.
3. Choose Antigravity for a task, queued work or recurring work. Configuration accepts an absolute CLI executable. Model discovery reads the current CLI model through the read-only /model command; use agy to change it, then refresh. This response does not provide the complete model catalog.
4. Review the result and changes. Continue reuses the exact conversation and workspace; Stop terminates the owned process tree.

An installed executable does not prove authentication. Access is validated when the agent starts. No credential files are read to invent a connected state. The existing CLI subscription login uses the OS credential store. Its identity is not pinned; changing that login can affect existing continuations. Multiple subscription logins do not yet have a verified isolation override.

Named Jackalope accounts use Google's documented Gemini API-key mode instead. Each profile has a separate HOME/USERPROFILE and .gemini/antigravity-cli/settings.json with modelProvider: "gemini". Jackalope requires an account-specific GEMINI_API_KEY and rejects a changed provider setting or missing key before launch. Keys are protected with Windows DPAPI, macOS Keychain or Linux Secret Service. Gemini API billing is separate from a Google subscription. Real two-account API-key execution and continuation require separate acceptance.

Execution and permissions

Prompts are encoded as a single JSON message on stdin. No shell interpolation or CLI slash-command execution is used. Each attempt gets one CLI process and one turn, with an explicit workspace directory in both launch arguments and context. This matters because a resumed headless conversation may otherwise look for a different checkout. The normal Jackalope worktree and review safeguards apply; workspace instructions are not a filesystem sandbox.

The adapter preserves the CLI's permission settings and never adds --dangerously-skip-permissions. A tool permission denial can coexist with a successful CLI exit; Jackalope records it as a failed attempt needing attention. Grant only the intended operation through the CLI's permission configuration and continue. Native terminal questions cannot be answered through Jackalope; agents should use the supplied Jackalope question bridge instead.

Only a valid final SUCCESS event, nonempty result, consistent conversation ID, successful exit and no recorded adapter error can become ready for review. Malformed, oversized, missing or contradictory protocol events cannot pass. The adapter bounds output and enforces a 30-minute attempt timeout; partial work and history remain available. This is a per-attempt limit, not a task deadline.

Usage uses per-step observations, deduplicated by step index. This avoids adding prior turns from cumulative result counters to a continuation. Fresh runs can fall back to the final usage envelope; missing resumed usage remains unknown. The observed CLI reports uncached input and cache reads separately, and includes thinking in output tokens. Jackalope adds cache reads to input and does not add thinking twice. Subscription quota is read separately from the CLI’s structured -p /usage --output-format json command. The reader checks the CLI version first (minimum 1.1.11), requires a successful zero-turn command receipt, and keeps model groups and reset windows distinct. Missing percentages remain unknown. Gemini API-key profiles use separate API billing and do not expose Antigravity subscription allowances.

Jackalope tools

The local authenticated HTTP bridge supplies project assignments, messages, questions/answers, browser evidence and recorded validation. Project-selected MCP connections can use on-demand discovery through that bridge. Direct project MCP injection fails with an actionable explanation. Antigravity's own configured MCP servers remain managed by its CLI; Jackalope does not rewrite global or workspace MCP configuration or place task credentials into source files.

HTTP calls remain subject to the CLI's shell/network policy. Discovery never authorizes side effects. An unavailable transport is reported, not bypassed. See orchestration capabilities for shared coverage.

Verification

Automated regression coverage and isolated native trials are described in CONTRIBUTING.md and SELF-DEVELOPMENT.md. Record detailed local receipts privately. Fixtures and source builds do not prove installed-app acceptance.