Antigravity CLI replaces Gemini CLI on June 18 — your free-tier agent tooling is on a clock

verified

Thursday, May 21, 2026

The News

Buried inside the I/O 2026 rollout, Gemini CLI is being retired, and Antigravity CLI replaces it; if you use Gemini CLI through a free account or Google AI Pro/Ultra, you have until June 18, 2026 to migrate. Enterprise Gemini Code Assist licences and API-key users keep it . Agent Skills, Hooks, Subagents and Extensions all carry over, so the move shouldn't hurt much; just don't get caught by the date . Migration details on the Google Developers blog. Separately, Google launched a new $100 AI Ultra plan, specifically tailored for developers, technical leads, knowledge workers and advanced creators, including 5× higher usage limits in the Gemini app and Antigravity than the AI Pro plan, plus 20TB of cloud storage .

The Read

The Gemini CLI deprecation is the single most practitioner-actionable item from I/O — and it's the one Google buried furthest down the announcement stack, which is exactly the pattern. The split between free-tier users (forced migration in 30 days) and enterprise license / API-key holders (no change) is doing two things at once: thinning the free user base before the AI Ultra upsell, and creating a hard line between hobbyist and paying agent developers. The $100/month tier isn't priced against ChatGPT Plus; it's priced against Claude Max and Cursor Pro, and the 5× usage uplift signals Google now expects an individual developer to be running multiple agents in parallel as the default. If you have any CI pipeline, internal tool, or side project routing through Gemini CLI on a free account, June 18 is a deployment risk, not a UX one.

Do This Week

Grep your codebase and CI configs for every `gemini` CLI invocation, every `gemini-cli` GitHub Action, and every shell script that shells out to it. For each one, confirm whether the account behind it is free/Pro/Ultra (must migrate) or API-key/Code Assist (safe). Anything still on a free account by June 1 should either be moved to Antigravity CLI in a feature branch or have an API-key fallback merged — not both, not later.

For Developer