On May 27, we wrote about the mechanics of Google’s Gemini CLI bait-and-switch: the 6,000 community PRs accepted, the Apache 2.0 promise, the proprietary replacement with no feature parity “out of the gate.” That was the announcement.
Today is the day.
As of June 18, 2026, Gemini CLI stops serving requests for Google AI free, Pro, and Ultra users. Any script, CI pipeline, cron job, or workflow calling gemini will either fail with a 404 or — worse — fail silently with no error surfaced to the caller. Gemini Code Assist IDE extensions are also shutting down for consumer accounts today.
The details of what actually broke are more specific, and in some cases worse, than what was announced in May.
The Quota Cliff Nobody Publicized#
The headline from May was “free tier ends June 18.” The fine print was more damaging.
Gemini CLI’s free tier ran at approximately 1,000 requests per day. Antigravity CLI’s free tier is capped at 20 requests per day — a 98% reduction.
This is not a minor adjustment. 1,000 requests per day is a functional development quota: it covers multiple coding sessions, automated test runs, CI linting passes, and exploratory use. 20 requests per day is a trial limit. You can meaningfully demo the product. You cannot use it as part of a working development workflow.
Google never announced this reduction prominently. It appeared in the migration documentation as a footnote. Developers who planned their migration assuming “Antigravity has a free tier like Gemini CLI did” are discovering today that the effective compute available to them is a fraction of what they had — even before paying.
For paid users the picture is also worse than expected. Google moved Pro users from a daily to a weekly compute cap in March 2026 — a change that reduced burst capacity even if the total remained the same. The weekly cap means a heavy Tuesday burns through a quota that doesn’t reset until the following Tuesday, which changes the practical usage profile substantially.
What’s Breaking in CI#
The second category of damage is in automated workflows, and it is characterized by a particularly frustrating property: silence.
Gemini CLI’s shutdown for consumer accounts is not implemented as an explicit deprecation error. Scripts calling gemini on affected accounts are not receiving a clear “this API key no longer has access” response in all cases. Several migration guides published in the past two weeks note that some automation failures are manifesting as timeouts or empty responses rather than HTTP 401s or 403s — which means existing error-handling logic that watches for authentication failures won’t catch them.
If you have CI pipelines that call Gemini CLI and treat a non-error exit code as success, those pipelines are silently no longer doing what you think they’re doing. This is the kind of bug that surfaces in production incidents, not deployment failures.
The correct fix is to run agy --version in your pipeline to confirm the Antigravity CLI binary is installed and responding before trusting any downstream output. But this requires knowing to look for the problem in the first place.
Who Actually Still Has Access#
The enterprise carve-out is real and worth understanding precisely, because it reveals what Google considers its actual customer.
Still working today, unchanged:
- Organizations with Gemini Code Assist Standard or Enterprise licenses
- Access via paid Gemini and Gemini Enterprise Agent Platform API keys
- Gemini Code Assist for GitHub via Google Cloud (though new installations stop after today)
Shut off today:
- Google AI Pro and Ultra personal accounts
- Free-tier Gemini CLI users
- Gemini Code Assist IDE extensions for consumer accounts
The carve-out draws a clean line: Google wants to keep enterprise contracts whole and free-tier users as a conversion funnel for Antigravity AI Ultra ($100/month). Individual developers on personal Pro accounts are, for practical purposes, being moved off the product.
This is a coherent business decision. It is not a developer-first one.
What Antigravity CLI Actually Is vs. What Was Promised#
Antigravity CLI (binary: agy) is a closed-source Go binary. It is not open-source. The source code has not been published, transferred to a foundation, or released under any license. The developers who contributed to Gemini CLI’s 6,000-PR open-source codebase are running a proprietary replacement they cannot inspect, fork, or audit.
What Antigravity CLI preserves from Gemini CLI: Agent Skills, Hooks, Subagents, and Extensions (now rebranded as Antigravity plugins). The core agent loop is intact. MCP server support carries over.
What is explicitly not guaranteed to carry over: the Python extension ecosystem. Google acknowledged at launch that “some edge-case behaviors from Gemini CLI’s Python extension ecosystem may not be present” in Antigravity. For teams that built custom Python extensions for Gemini CLI — and given the 6,000-PR contribution history, there were many — this means an undetermined amount of functionality that worked yesterday may not work today, with no clear migration path for the gap.
This is the practical consequence of closing the source. Open-source migration gaps can be fixed by the community. Closed-source gaps wait for Google’s roadmap.
Where Developers Are Going#
The migration patterns emerging in the past 48 hours cluster into four destinations:
Claude Code is the primary beneficiary. The developer profile that used Gemini CLI — terminal-native, free/Pro tier, not enterprise — overlaps substantially with the Claude Code $20 Pro plan demographic. Claude Code’s MCP ecosystem (6,400+ servers), Routines for automation, and terminal-native architecture covers most of what Gemini CLI was used for, at higher capability. The trade-off is cost: Claude Code Max starts at $100/month.
OpenCode (the open-source Go terminal agent with 147K GitHub stars) is the ideological response. Developers burned by Gemini CLI’s open-source reversal are migrating to a tool that cannot execute the same bait-and-switch: OpenCode is Apache 2.0, community-governed, and supports 75+ LLM providers. The capability ceiling is lower than Claude Code or Antigravity, but the infrastructure risk is structurally different.
Aider captures the subset of Gemini CLI users who were primarily using it for git-integrated coding assistance with minimal agentic workflow. Aider is Python-based, open-source, and well-established.
Cursor (or rather, now SpaceX’s Cursor) is attracting users who want an IDE-embedded experience instead of terminal-native. A portion of the Gemini CLI user base was using it as a coding assistant inside an IDE-adjacent workflow; Cursor’s free tier and polished interface captures some of that segment.
The common thread across all four destinations is distrust of Google’s infrastructure commitments. The developers choosing these tools today are not choosing them because they are technically superior in every dimension. Some of them are choosing them because they want something that will still exist in twelve months under terms they can predict.
The Compounding Trust Deficit#
Google’s developer trust problem did not start with Gemini CLI. It started with Google Reader, Stadia, and the long list of shutdowns collected at killedbygoogle.com. But in the AI developer tools market — which is younger and where infrastructure commitments have longer time horizons — the Gemini CLI episode is acute.
The pattern: ship a compelling free tool to capture developer mindshare, accept open-source contributions that improve the product, then shut down the free tier and replace it with a proprietary product at a price point that excludes the community that built it. Run that playbook once and it’s a business decision. Run it twice — Meta ran a version of it with Avocado and the Llama ecosystem earlier this year — and it becomes an industry-wide signal.
The signal developers are reading today: free AI infrastructure from hyperscalers is a liability, not a capability. Budget the cost of your tooling from day one, or budget the cost of migration later.
That lesson is worth more than the 20 free requests per day Antigravity is offering.
Sources:
- Gemini CLI and Code Assist shut down for consumers this week amid Antigravity focus — 9to5Google
- Google Kills Gemini CLI on June 18: Builder Migration Guide — AI Builder Club
- Gemini CLI → Antigravity CLI Migration Guide — Agentpedia
- Google Sunsets Gemini CLI on June 18: Forced Migration to Antigravity CLI Breaks Existing Automation — Groundy
- An important update: Transitioning Gemini CLI to Antigravity CLI — Google Developers Blog
- Gemini CLI will stop working from June 18, 2026 — Hacker News
- Gemini CLI Dies June 18: The Antigravity Migration Guide — DigitalApplied
- Bye-bye, Gemini CLI; Google’s gone and swapped you for a closed-source AI — The Register
