Repository navigation
Gemini CLI > Antigravity CLI - June 18, 2026 DEADLINE #778
Description
Need to update Codev to be compatible with Antigravity CLI as Gemini CLI is being retired on June 18, 2026.
On June 18, 2026, Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro and Ultra, as well as those using it free of charge using Gemini Code Assist for individuals.
https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli
Activity
waleedkadous commentedon Jun 2, 2026
Architect context for the builder
Goal: migrate consult's Gemini lane off the
geminiCLI (its subscription path retires June 18, 2026) to the Antigravity CLI.Current integration (what to replace):
packages/codev/src/commands/consult/index.ts:38—gemini: { cli: 'gemini', args: ['--model', 'gemini-3.1-pro-preview'], envVar: 'GEMINI_SYSTEM_MD' }. consult shells out togemini, auth viaGEMINI_API_KEY.packages/codev/src/commands/consult/usage-extractor.ts—extractGeminiUsage()parses the gemini CLI's--output-format json(stats.models[].tokens) for token counts + cost. Pricing table there was just refreshed for 3.x models.Antigravity CLI is installed locally — inspect the real interface, don't guess:
~/.antigravity/antigravity/bin/antigravity(v1.107.0) → runantigravity --help.Must-preserve capabilities (spec each against what Antigravity actually supports):
gemini-3.1-pro-preview; consider defaulting reviews to Gemini 3 Flash to conserve Antigravity credits).GEMINI_SYSTEM_MD).usage-extractor.tscost tracking — Antigravity bills in AI credits (rate undisclosed); figure out how it reports usage.Key design question for the spec: does the Antigravity CLI even support non-interactive scripted reviews + machine-readable output? If not, what's the fallback (e.g. keep the
geminiCLI on a Developer-API API key, which is a separate product that may survive past June 18)?Ref: https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli
waleedkadous commentedon Jun 2, 2026
Auth decision: OAuth-only (verified).
Confirmed against the official antigravity-cli docs (README "Authentication") +
agy --help:agyauthenticates via system keyring → Google Sign-In (OAuth) only. No API-key path exists — noGEMINI_API_KEY/GOOGLE_API_KEYenv var, no--keyflag, no auth subcommand; CHANGELOG confirms "OAuth token persistence". So OAuth/subscription is the only option, not a preference.Decision: implement OAuth-only as specced. The interactive first-run auth (no headless CI) is therefore unavoidable → the non-blocking-skip-in-CI design is retained.
Follow-up: API-key auth support (for headless/CI or non-subscription users, likely via the Gemini Developer API) is tracked in #965 — deferred, not blocking this work.
[PIR cluesmith#929] doctor: bar gemini as architect (builder-only); d…
[Spec 1338][Phase: review] docs: refresh review metrics + log follow-…