Google gave Gemini CLI users 30 days. The developer blog post1 published May 19, 2026 announces that the CLI, plus Gemini Code Assist IDE extensions, stop serving requests on June 18 for everyone except enterprise license holders. The replacement is Antigravity CLI, a separate Go binary, and Google explicitly warns there will be no 1
feature parity at launch.What changed
The sunset covers Gemini CLI and all Gemini Code Assist IDE extensions. After June 18, 2026, these tools stop serving requests for Google AI Pro, Ultra, and free-tier users. Gemini Code Assist for GitHub is also affected: no new installations on GitHub organizations after that date, with existing installations stopping in the following weeks.
The timeline is tight. The cutoff is June 18. Teams running Gemini CLI in CI pipelines, shell scripts, or agentic loops have roughly four weeks to identify every invocation, rewrite it against the new binary and auth model, test, and ship.
What Antigravity CLI is
Antigravity is not a renamed Gemini CLI. It is a separate product built in Go for faster execution. The getting started guide2 describes a desktop app built as a VS Code fork with two views: Editor and Agent Manager.
Features carried forward from Gemini CLI include Agent Skills, Hooks, Subagents, and Extensions, though Extensions have been renamed to “Antigravity plugins.” Antigravity 2.0.1 shipped May 19, 2026 alongside the sunset announcement, according to Wikipedia.3 The original public preview launched November 18, 2025 alongside Gemini 3.
One notable difference: Antigravity supports multiple AI models, including Anthropic’s Claude Sonnet 4.6, Claude Opus 4.6, and an open-source OpenAI variant called GPT-OSS-120B,3 not just Google’s own Gemini models. This positions it as a multi-model client rather than a single-vendor CLI.
What is missing
Google states directly that there will not be 1
feature parity between Gemini CLI and Antigravity CLI at launch. The blog post does not enumerate which specific features are absent, which means the actual migration pain is almost certainly understated. Teams discover the gaps by hitting them.The absence of a published compatibility matrix is itself a signal. If the gaps were minor, Google would list them. Leaving them unspecified lets the announcement read as a smooth transition while offloading the discovery cost onto users.
Who is affected and who gets a carve-out
Enterprise customers on Gemini Code Assist Standard or Enterprise licenses retain Gemini CLI access unchanged.
Everyone else is on the clock. The 100,000+ GitHub stars, 6,000 merged pull requests, and hundreds of contributors on Gemini CLI1 represent a large installed base now forced onto a new binary with acknowledged feature gaps.
The enterprise carve-out creates a two-tier community. Paid customers stay on the tool they built around. Free and Pro users migrate or stop. That split fragments documentation, bug reports, and community support at exactly the moment migration demands the opposite.
The migration friction
Every CI pipeline, shell script, agentic loop, and IDE configuration that calls gemini needs to be rewritten against the new binary. The binary name is different, the auth model is different, the plugin naming convention has changed (Extensions are now “Antigravity plugins”), and the surface area is different because feature parity is explicitly absent.
For a team that wired Gemini CLI into a single developer’s shell, this is an afternoon. For a team that embedded it in multi-stage CI with model-specific flags, prompt templates, and error-handling paths, this is a multi-day rewrite with a testing phase.
The 30-day window compounds the problem. Enterprise DevOps teams commonly run on two-week sprint cycles. A 30-day deadline announced mid-sprint means at most one sprint to plan, execute, and verify the migration before the old tool stops working.
The trust tax
The direct migration cost is measurable in engineering hours. The indirect cost is harder to quantify but probably larger.
Gemini CLI had genuine community investment. Over 100,000 GitHub stars and 6,000 merged PRs1 are not vanity metrics; they represent real work by real engineers who chose to build on Google’s CLI tooling. Google is now telling those engineers to do it again on a different product, with explicit acknowledgment that the new product does less.
Every shop that standardized on Gemini CLI for automation now has to recalculate the expected lifespan of any future Google CLI tool. If Gemini CLI lasted roughly a year before being replaced (it launched in early 2025), what is the expected lifespan of Antigravity CLI? That uncertainty is a cost. It shows up in architecture review meetings when someone asks whether to build on Antigravity or on a competitor’s tool that has not yet been renamed out from under its users.
Google frames this as “transitioning” and “unifying.” The practical experience for affected teams is a forced rewrite with a hard deadline and no compatibility layer. The framing does not match the lived experience, and engineers notice the gap.
What to consider instead
Teams re-evaluating their CLI tooling have options beyond Antigravity:
- Claude Code (Anthropic): CLI-based agent with strong CI integration. No history of forced binary migration.
- OpenAI’s CLI tools: Functional but less community momentum than Claude Code or Gemini CLI had.
- Cursor agents: IDE-integrated, not CLI-native, so not a direct replacement for pipeline use cases.
- Remain on Gemini CLI via enterprise license: Works for paid tiers, but locks you into a deprecated product with a shrinking community.
The competitive dynamic matters. Anthropic and OpenAI have not yet forced a comparable migration on their CLI users. Google just did, on 30 days’ notice, with acknowledged feature gaps. For teams evaluating where to invest automation infrastructure for the next 12-18 months, that difference in track record carries real weight.
Frequently Asked Questions
What is the actual command to invoke Antigravity CLI?
The new binary is invoked via agy, replacing the gemini command. Every shell alias, CI stage, shebang line, and PATH reference to the old binary will need updating — the command name is not backward-compatible.
Can I keep Gemini CLI working after June 18 without an enterprise license?
Yes, but through a different mechanism than the enterprise carve-out. Google states the CLI remains accessible via paid Gemini and Gemini Enterprise Agent Platform API keys. This path is separate from Code Assist Standard/Enterprise licenses and is not covered in the migration guide, so expect thinner documentation and community support.
Do Agent Skills and Hooks carry over with identical flag names and config syntax?
Probably not. Antigravity is a ground-up Go rewrite rather than a fork of Gemini CLI’s original stack, so flag names, environment variable conventions, and config file schemas are likely different even for features Google lists as ‘carried forward.’ Teams should treat every shared feature name as requiring verification rather than drop-in compatibility.
Has Google committed to a product lifecycle or sunset policy for Antigravity CLI?
No. Antigravity’s public preview launched just six months ago (November 18, 2025), and the replacement of Gemini CLI roughly one year after that product’s own launch sets a concrete precedent. The absence of any published lifecycle commitment is notable for teams investing in long-lived automation on the platform.