Antigravity
Install, authenticate, and resume Google's Antigravity CLI (agy) inside Daintree.
Antigravity
Antigravity CLI is Google's terminal coding agent and the successor to Gemini CLI for personal Google accounts. Its binary is agy. It shares an agent engine and its settings with the Antigravity desktop app, and runs as a process in its own Daintree terminal panel with full PTY emulation, like every other built-in agent.
| Command | agy |
|---|---|
| Shortcut | None in Keyboard Shortcuts by default (see below) |
| Color | Blue (#4285F4) |
| Default rendering | Alt-screen escapes are blocked; output lands in Daintree's scrollback |
| Permission bypass | --dangerously-skip-permissions (per agent or preset, or inherited from the global switch) |
| Resume | agy --conversation <id>, falling back to agy -c |
| Platforms | macOS, Windows, Linux |
Antigravity has no default binding in the keybinding system, so Settings > CLI agents > Antigravity > Keyboard shortcut starts empty. Until you assign one there, the Terminal menu's New Antigravity item (shown once agy is installed) still carries Cmd+Alt+A, or Ctrl+Alt+A on Windows and Linux, from the agent definition.
Install & Authenticate
See Google's current setup instructions for installation and sign-in.
Google ships an install script for each platform. It places agy at ~/.local/bin/agy on macOS and Linux, and under AppData\Local\agy\bin on Windows. Update later with agy update. Daintree's in-app install prompt has no command for Antigravity; it links to Google's announcement of the move from Gemini CLI.
curl -fsSL https://antigravity.google/cli/install.sh | bashirm https://antigravity.google/cli/install.ps1 | iex From CMD instead of PowerShell: curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd.
curl -fsSL https://antigravity.google/cli/install.sh | bashRun agy once. It first checks your operating system's keyring and signs you in silently if a saved token is there. Otherwise it opens a browser for Google sign-in, with either a personal Google account or a business (Gemini Enterprise) account. Over SSH it prints an authorization URL and waits for the code you paste back. /logout clears the saved credentials.
Antigravity inherits the Gemini CLI's credential layout, so Daintree checks ~/.gemini/oauth_creds.json and ~/.gemini/google_accounts.json, or a GOOGLE_API_KEY environment variable, when deciding whether the agent shows as ready. On a first run that authenticated purely through the keyring those files may not exist yet, and the badge can read No credentials detected while agy itself works. The reverse also happens: agy doesn't read GOOGLE_API_KEY, so that variable can make the badge look ready without giving the CLI a credential. Launch it and see; the badge is a probe, not a verdict.
"modelProvider": "gemini" in ~/.gemini/antigravity-cli/settings.json and export GEMINI_API_KEY. The CLI reads the key only from that variable, and only with that provider set: GOOGLE_API_KEY and .env files are ignored. Remove modelProvider to go back to Google sign-in.How Daintree Launches It
Antigravity's first launch asks you to pick a color scheme, a rendering mode, and whether you trust the directory. Pick either rendering mode: Daintree blocks alt-screen escapes for this agent regardless, so output flows into its own scrollback and stays selectable. Resizes are applied once the pane settles rather than on every intermediate width, because the TUI redraws its whole frame on each resize.
Antigravity's bypass flag is --dangerously-skip-permissions. Daintree injects it when you turn bypass on for the agent or a preset, or when the global Skip permission prompts switch is on and the agent inherits it.
Antigravity 1.5.5 or later can run the Daintree Assistant, beside Claude Code and Codex. For an Assistant session Daintree writes the MCP servers into the session folder's .agents/mcp_config.json and passes a session-only --settings file that trusts that folder and allows Daintree's own servers. Your saved Antigravity settings are never written; for that session Daintree's allow list stands in for yours, while your own ask and deny rules still apply. An Antigravity pane you launch for coding is different: Daintree doesn't hand it its MCP servers at launch. The agent launches from the roster like any other.
State detection
Daintree recognizes Antigravity's spinner, prompt, and approval dialogs from observed output. Antigravity prints no completion banner, so a finished turn normally settles into Waiting, ready for the next instruction. This does not mean it failed. A custom /statusline may remove footer cues; detection then falls back to timing and silence. Terminal-title signals are not used because Antigravity leaves them off by default.
Resuming Sessions
Daintree captures Antigravity's conversation ID from the resume hint it prints on exit and resumes with agy --conversation <id> rather than the path-scoped shorthand, so a resume targets the exact conversation. Quit cleanly with /quit so the ID is captured; when capture misses, the fallback is agy -c. Whether a conversation survives moving or renaming the project is unconfirmed, so the move-or-rename preview marks it unverified instead of promising either outcome. For the resume mechanics across all agents, see Session Resume.
.antigravitycli/ directory at the root of the project it runs in. Add it to your .gitignore so it doesn't turn up in a review diff.Integration reference
This guide describes Daintree's checked-in integration. Its agent definition records the launch command, install guidance, authentication probes, rendering capabilities, and resume support. Authentication badges report local evidence; the CLI still owns sign-in and provider access. After changing an installation, use Re-check in Settings > CLI agents; restart Daintree if its inherited PATH has changed.