Google / developers.googleblog.com Google Accepted 6,000 Gemini CLI Contributions, Then Closed the Project for Enterprise
On May 19, Google announced that Gemini CLI's free access ends June 18. The replacement is Antigravity CLI, a closed-source Go tool with a near-useless 20-request/day free tier. Community reaction to the open-source bait-and-switch has been sharp.
Google announced on May 19 that Gemini CLI’s free-tier API access will end on June 18. The tool is transitioning to a new product called Antigravity CLI, which is closed-source, built in Go, and aimed at enterprise teams. The open-source Gemini CLI repo stays up with its Apache 2.0 license — but without a Google-operated backend, it stops working for most users on June 18.
The timing is the problem. Gemini CLI launched in June 2025 as a genuine open-source project. It accumulated over 100,000 GitHub stars and more than 6,000 merged pull requests from external contributors. That’s a meaningful amount of community labor. Accepting thousands of contributions and then pivoting the project to a closed enterprise product is the kind of move that gets remembered.
What’s changing
Until June 18, Gemini CLI offers 1,000 free requests per day through a personal Google account. That’s enough to do real work. After June 18, free access drops to 20 agent requests per day on the Antigravity CLI free tier.
Google AI Pro and Ultra subscribers ($7.99/mo and $249.99/mo) also lose access on June 18. The only users who keep their current access are enterprises on Gemini Code Assist Standard or Enterprise licenses.
Paid Antigravity CLI tiers start at $20/month for Pro and $200/month for Ultra. Google hasn’t published a migration matrix that clearly maps current free-tier usage patterns to what they’d cost after the switch.
What Antigravity CLI is
The Antigravity CLI GitHub org describes it as an “agent-first development platform.” It’s a closed-source Go binary. Google says it will include features for enterprise teams — org-wide controls, spend tracking, shared context — that the open-source TypeScript tool doesn’t have.
That framing positions it as a genuine product upgrade rather than just a cost-cutting move. The problem is that upgrading means leaving behind an active open-source ecosystem and replacing it with something developers can’t inspect, fork, or contribute to.
The community response
The GitHub discussion thread announcing the transition has over a thousand replies. The core complaint isn’t about pricing: developers are annoyed that Google accepted contributions to an open-source project and then routed the commercial value of that work into a closed successor.
The Register, The New Stack, and several developer newsletters all covered it this week. The framing is consistent: “open-source bait-and-switch.” That’s a reputational cost that follows a company for years, especially with the developer community.
Google hasn’t commented on the optics directly.
What developers are doing
A few things are happening in parallel. Some developers are migrating to Antigravity CLI’s paid tiers. Others are switching to alternatives: Claude Code, Codex CLI, and Gemini CLI forks are the most commonly mentioned in the discussion thread. There’s also at least one active community fork attempting to keep the open-source project alive with alternative backends.
The irony is that the alternatives — Claude Code and Codex CLI in particular — are also closed-source, so the fork camp has limited options. The real story here is that the 20-requests/day free tier on Antigravity isn’t a free tier in any practical sense. It’s a trial cap.
June 18 is three weeks out. Developers who built workflows around Gemini CLI’s generous free access now have a deadline.