Google Quietly Killed Gemini CLI While Everyone Was Celebrating I/O
Part 4 of 5 in the Google I/O 2026 Review series.
There is a term in media strategy called "bad news burial." You wait for a high-traffic news cycle — a holiday, a natural disaster, an election night — and drop the announcement you don't want people to read. The hope is that the noise drowns it out.
On May 19, during Google I/O Day 1, while developers were still digesting Flash 3.5 benchmarks and the Managed Agents API, Google published a blog post announcing that Gemini CLI will be discontinued on June 18, 2026.
Not on stage. Not in the keynote. A blog post and a GitHub Discussion, timed to land under the loudest news cycle of the developer year.
Gemini CLI gave you 1,000 agent requests per day. Antigravity CLI gives you 20.
The Timing Was a Choice
Every major announcement at I/O got a keynote slot. Flash 3.5 beating Pro on benchmarks — keynote. Managed Agents API with 30+ integrations — keynote. Even Project Aura's 80-gram XR glasses got stage time.
The discontinuation of an Apache 2.0 open-source CLI used by thousands of developers? Blog post. Buried in the I/O news flood.
This matters because the announcement was not a minor change. It was a license model reversal, a free tier reduction of 98%, and a 30-day shutdown notice — all rolled into one. Any one of those would deserve its own conversation. Together, they constitute one of the sharpest reversals in developer tooling this year.
What Changed — The Numbers
Here is what developers are losing and what they are getting, based on what Google has disclosed:
| Gemini CLI | Antigravity CLI | |
|---|---|---|
| License | Apache 2.0 (open source) | Closed source ("possibility" of open-sourcing mentioned, no commitment) |
| Free tier | 1,000 requests/day + 60 RPM | 20 requests/day (free individual plan, $0/mo) |
| Reduction | — | 98% fewer free requests |
| Agent Client Protocol (ACP) | Supported | Community reports suggest not yet available |
| Project memory | Supported | Community reports suggest not yet supported for markdown files |
| Ctrl+C behavior | Normal exit | Some users report unreliable exit (Discussion #27274) |
| Documentation | Community-maintained, extensive | Sparse at launch |
| Shutdown notice | — | ~30 days (May 19 → June 18) |
| Enterprise | Supported | Maintained |
Free tier numbers from Gemini CLI GitHub README and Antigravity pricing.
The enterprise tier is maintained. Individual developers and small teams — the people who built their daily workflows around 1,000 free requests — get 20. That is not a "reduced free tier." That is a rounding error.
The Open Source Question
Gemini CLI was not just open source by license. It was open source by practice. Thousands of pull requests and issues from external contributors. Bug fixes, extensions, documentation improvements — the community was building the product alongside Google.
That is the implicit contract of open source: you contribute labor under an open license, and the project stays open and accessible. Apache 2.0 does not legally require this. But the social contract does, and breaking it has consequences that Apache 2.0 cannot measure.
The code those contributors wrote under Apache 2.0 is now feeding a closed-source product that the same contributors can barely use — 20 requests a day does not support any real development workflow.
Legally, nothing was stolen. Socially, something was taken.
The Pattern
This is not a new playbook. The sequence:
- Launch open source with a generous free tier. Attract developers. Build community.
- Accumulate contributions. External developers improve the product at zero cost under an open license.
- Transition to closed source. The community-built product becomes proprietary. Free access drops to nominal levels.
- Monetize through enterprise. Meaningful access requires paid licenses.
The "Google Graveyard" meme resurfaced immediately in the Hacker News thread. But this is different from shutting down a consumer app. Consumer apps have users. Open-source projects have contributors — people who invested engineering time into something they were told would remain open.
What Developers Are Doing Right Now
The HN and GitHub threads paint a clear migration picture:
- Claude Code is the most frequently mentioned alternative. Developers cite the plugin/skills ecosystem and extensibility.
- OpenAI CLI (Codex) gets mentions from developers who want to stay with a major provider.
- Local/self-hosted alternatives — Ollama-based setups, open-weight model wrappers — are attracting developers who now distrust cloud-dependent CLIs entirely.
- Gemini CLI forks from the last Apache 2.0 commit exist, though a fork without Google's model access has uncertain long-term viability.
The irony: Google's move may have driven more adoption to competitors than any competing marketing campaign could have achieved.
What This Does Not Solve
The 60 RPM question. Gemini CLI offered 60 requests per minute. Google has not clearly disclosed whether Antigravity maintains this rate limit for paid tiers. If you are evaluating a switch, verify this before committing.
The fork path. Gemini CLI's Apache 2.0 code is still available. A community fork is technically possible. Practically, a fork without Gemini model access has limited utility — someone would need to wire it to alternative providers, and that is a significant effort with no clear owner.
Whether Antigravity improves. Google mentioned the "possibility" of open-sourcing Antigravity in the future. Missing features might ship quickly. The free tier might expand. But "possible" is not a commitment, and developers building workflows need commitments.
Google's internal reasoning. Serving 1,000 free requests per day per user at scale is not cheap. The economics may have forced this decision. But the execution — 30-day notice, missing features in the replacement, a free tier reduced to near-irrelevance, and the timing — turned a business decision into a trust problem.
The Lesson
If your workflow depends on a vendor-controlled tool, you have two options:
- Accept the dependency and price in the risk that the vendor changes terms. Budget migration time from day one.
- Build on open standards and self-hostable tools where the switching cost stays low.
Neither option is wrong. But pretending the risk does not exist — that is the mistake Google just made visible.
The developers who contributed to Gemini CLI under Apache 2.0 did nothing wrong. They participated in open source the way it is supposed to work. What failed was not the license. It was the assumption that a trillion-dollar company's incentives would stay aligned with theirs.
Remember this the next time a major provider launches something generous and open. The question is not whether it is good today. The question is: what happens when your workflow depends on it, and the economics change?
Part 5 will cover the overall I/O scorecard — what the four wins and four misses tell us about where Google is heading.
If you migrated off Gemini CLI already, I'd like to hear what you moved to and what the transition cost was. Drop a comment or find me on GitHub.
Top comments (0)