Antigravity

Install, authenticate, and resume Google's Antigravity CLI (agy) inside Daintree, the successor to the retired Gemini CLI.

Reviewed Aug 18, 2026

Antigravity

Antigravity CLI is Google's terminal coding agent and the successor to the retired Gemini CLI. 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 by default — assign one in Keyboard Shortcuts
Color	Blue (#4285F4)
Default rendering	Alt-screen escapes are blocked; output lands in Daintree's scrollback
Permission bypass	`--dangerously-skip-permissions`
Platforms	macOS, Windows, Linux

Install & Authenticate

Google ships a native installer script. It places agy at ~/.local/bin/agy on macOS and Linux, and under AppData\Local\agy\bin on Windows.

curl -fsSL https://antigravity.google/cli/install.sh | bash

irm https://antigravity.google/cli/install.ps1 | iex

curl -fsSL https://antigravity.google/cli/install.sh | bash

Run agy once. It first tries your operating system's keyring — Keychain, Secret Service, or Credential Manager — and signs you in silently if a token is already there. Otherwise it opens a browser for Google sign-in. Over SSH it prints an authorization URL and waits for the code you paste back. /logout clears the stored credentials.

Antigravity inherits the Gemini CLI's credential layout, so Daintree checks ~/.gemini/oauth_creds.json and ~/.gemini/google_accounts.json, or the 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 agent can read as "Needs login" while agy itself works. Launch it and see; the badge is a probe, not a verdict.

Note

To run headless with your own key, set modelProvider to gemini in ~/.gemini/antigravity-cli/settings.json and export GEMINI_API_KEY. The CLI reads the key only from that variable — setting it without the provider does nothing, and setting the provider without it stops the CLI from starting.

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; the global "skip permission prompts" switch passes Antigravity over, because the agent does not declare bypass support yet.

Daintree does not yet wire Antigravity into the Daintree Assistant — that path needs its settings-overlay and MCP-injection formats verified first — so the agent launches from the roster like any other but is not offered as the assistant.

Resuming Sessions

Daintree captures Antigravity's conversation ID 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.

Tip

Antigravity writes per-workspace state into a .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.