Google Antigravity CLI Setup

Configure Google Antigravity CLI (agy) with a QCode.cc key: set modelProvider in settings.json, then point GEMINI_API_KEY and GOOGLE_GEMINI_BASE_URL at QCode's Gemini endpoint

Last verified: 2026-09-18 · 📄 Per official docs (Antigravity CLI 1.2.x (auto-updater manifest 1.2.6, checked 2026-09))

At a glance¶

⚠️ Migrating from Gemini CLI? The official post of 2026-05-19 says, verbatim, that from 2026-06-18 Gemini CLI and the Gemini Code Assist IDE extensions "will stop serving requests" — for Google AI Pro and Ultra, and for people using it free of charge on a personal account. Enterprise paid keys are unaffected: the same post states that Gemini CLI remains accessible via paid Gemini and Gemini Enterprise Agent Platform API keys. What launched that day was Antigravity CLI and Antigravity 2.0; the Antigravity IDE itself shipped earlier, on 2025-11-18. If you followed Gemini CLI Integration before, switch to this page.

Google Antigravity is Google's successor to Gemini CLI for consumer sign-ins. It ships as three pieces: a desktop IDE, the Antigravity CLI (agy, written in Go), and an SDK. This page covers the CLI only: pointing it at QCode.cc as its model upstream.

🔴 Read this first: Gemini protocol only¶

Antigravity CLI's custom endpoint is Gemini-compatible, set through the GOOGLE_GEMINI_BASE_URL environment variable. The official troubleshooting table says, verbatim, that gemini is "the only accepted value" for modelProvider — so this route cannot take an OpenAI-compatible endpoint, and through QCode it can only serve Gemini-family models.

For Claude or GPT, use a different client — Claude Code, Codex CLI, Cline, Zed. Which protocol serves which models is documented in Endpoints & API Paths.

🔴 The Antigravity IDE (2.0 desktop app) cannot be connected¶

The Antigravity desktop IDE currently has no official BYOK or custom-provider hook, so its built-in agent model cannot be swapped for a third-party endpoint. Community projects work around this with a local intercepting proxy, but that is a reverse-engineered path with no official support, and this page does not recommend it.

The piece that connects to QCode is the CLI (agy), not the IDE.

Prerequisites¶

• A QCode.cc API key (starts with cr_), from the console
• Familiarity with Endpoints & API Paths

Step 1: Install Antigravity CLI¶

Defer to the official install docs:

curl -fsSL https://antigravity.google/cli/install.sh | bash
# installs to ~/.local/bin/agy

curl -fsSL https://antigravity.google/cli/install.sh | bash
# installs to ~/.local/bin/agy

irm https://antigravity.google/cli/install.ps1 | iex
# installs to C:\Users\<username>\AppData\Local\agy\bin

curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd

The official install page mentions --skip-aliases and --skip-path, but that is the Windows behaviour: install.ps1 / install.cmd forward arguments to agy install, while install.sh on macOS / Linux only accepts -d, --dir <path> and -h, --help and exits on anything else. Do not copy those two flags on macOS / Linux.

Step 2: Switch to API-key auth (skip the Google sign-in)¶

By default agy reads your OS keyring or opens a browser for Google account sign-in. To use an API key instead, edit (or create) ~/.gemini/antigravity-cli/settings.json:

{
  "modelProvider": "gemini"
}

With this set, agy skips the sign-in screen and opens the main interface directly, reading the GEMINI_API_KEY environment variable instead.

🔴 If "modelProvider": "gemini" is set but GEMINI_API_KEY is missing, the CLI will not start. Both are required together.

Step 3: Point the key and endpoint at QCode¶

export GEMINI_API_KEY="cr_your_qcode_key"
export GOOGLE_GEMINI_BASE_URL="https://api.qcode.cc/gemini"

Add them to ~/.zshrc / ~/.bashrc to persist. On Windows PowerShell:

$env:GEMINI_API_KEY = "cr_your_qcode_key"
$env:GOOGLE_GEMINI_BASE_URL = "https://api.qcode.cc/gemini"

Stop GOOGLE_GEMINI_BASE_URL at /gemini and leave /v1beta out: the official example is a bare address (export GOOGLE_GEMINI_BASE_URL="https://your-endpoint.example.com"), and the client adds the version segment and request path itself. agy is a closed-source Go client — Google documents neither the joining rule nor whether a trailing / is normalised (the SDK behind Gemini CLI does strip one), so we follow the documented shape instead of guessing at edge cases. This is the opposite of OpenCode's google provider (which does need /v1beta); the difference is explained in Endpoints & API Paths.

From mainland China, swap the host for https://asia.qcode.cc/gemini (Asia node, nearest of HK/JP); the key is unchanged. us / eu work the same way.

When authenticating with GEMINI_API_KEY, /logout does nothing — there is no stored session to clear.

Step 4: Verify connectivity¶

Test QCode's Gemini endpoint directly, bypassing the tool:

# List the Gemini models you can currently call
curl -s https://api.qcode.cc/gemini/v1beta/models \
  -H "x-goog-api-key: $GEMINI_API_KEY"

# Send a minimal request (use a model id from the list above)
curl -s "https://api.qcode.cc/gemini/v1beta/models/gemini-2.5-flash:generateContent" \
  -H "x-goog-api-key: $GEMINI_API_KEY" \
  -H "content-type: application/json" \
  -d '{"contents":[{"parts":[{"text":"ping"}]}],"generationConfig":{"maxOutputTokens":16}}'

• JSON containing candidates → endpoint and key are both fine
• 401 → the path is right; the key is missing or wrong

Treat the live query as authoritative for which models exist — do not copy a fixed list from any document, including this one. The ids returned by that first curl are what this QCode leg can serve; the full catalogue and prices are on qcode.cc/models.

One caveat: the agy /model panel and agy --model=... use product display names (shaped like Gemini 3.5 Flash). Google does not document how an id from the API maps to a panel entry when a custom endpoint is configured, nor whether that list comes from your endpoint at all. If your model is missing from the panel, there is no further official guidance — we have not tested this, so we describe it as-is.

Once the endpoint checks out, run a conversation in agy.

Vision input vs. image generation¶

Tools like agy can read images — feed them a UI screenshot, an error screenshot or an architecture diagram and let the model write code or debug from it. That is a different thing from generating an image:

• Vision input: reference an image file path in your prompt, or paste / drag an image in. Gemini models have vision. Typical uses: rebuilding a UI from a design, locating a bug from an error screenshot, reading an architecture diagram.

• Image generation: requires the dedicated gpt-image-2 model on QCode's image endpoint — see gpt-image-2 Image Generation.

Troubleshooting¶

Next¶

• Endpoints & API Paths — protocol × model-family table
• Gemini CLI Integration — the predecessor (enterprise keys still work)
• Subagents — orchestrating background agents
• Automation & CI/CD — headless mode and scripting

No QCode key yet? One cr_ key covers Claude, GPT, Gemini and image models (on different protocols — see the table above). See pricing to get started.