Gemini CLI Dies in 17 Days: Google Forces 105,000 Stars Into a Walled Garden
When Google shipped Gemini CLI in 2025, it was one of the more honest open-source plays we’d seen from a Big Tech company. Terminal-based AI coding agent, Apache 2.0 licensed, 6,000 merged pull requests, hundreds of community contributors. It hit 105,000 GitHub stars and 14,000 forks. The developer community showed up — because it was genuinely useful and genuinely theirs.
Then, on May 19, 2026, Google announced that on June 18 — exactly 17 days from now — Gemini CLI and the Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro, Ultra, and free tier users. The replacement is Antigravity CLI: a closed-source, Go-based “agent-first development platform” that shares its backend with the Antigravity 2.0 desktop application.
The official announcement, authored by Dmitry Lyalin (Group Product Manager) and Taylor Mullen (Principal Engineer), frames this as a natural evolution. Developers’ workflows have “outgrown those early days of 2025,” they write. You now need “multiple agents communicating with each other to split up the work and solve complex problems.” The terminal tools need to “share a unified backend with the rest of your workflow.”
There’s nothing technically wrong with any of that. Multi-agent orchestration is a legitimate upgrade. Go is a reasonable choice for a snappier CLI. And yes, Agent Skills, Hooks, Subagents, and Extensions are being carried over as Antigravity plugins.
What’s worth examining is what’s not being carried over: the open-source licence, the community-driven development model, and the principle that a tool with 105,000 stars and 6,000 merged PRs should remain something developers can fork, audit, and improve themselves.
The enterprise carve-out
There’s a telling asymmetry in the announcement. Enterprise customers running Gemini Code Assist Standard or Enterprise — or those using paid Gemini API keys — are unaffected. Gemini CLI continues for them. The wall only closes around Pro subscribers, Ultra subscribers, and free users.
In other words: if you’re a company writing a Google Cloud bill, you keep the open-source tool. If you’re an individual developer, you don’t. That’s not a technical decision. That’s a product strategy decision dressed up as a platform consolidation.
The naming problem
Google hasn’t helped itself with the branding. “Antigravity” was already the name of Google’s IDE (a VS Code fork, more Cursor-like than CLI). Now there’s Antigravity 2.0 (the desktop app), Antigravity CLI (the terminal replacement), and presumably the original Antigravity IDE still lingering somewhere.
The Hacker News thread on the announcement — 406 points, 210 comments in 12 days — is littered with confusion. Developer tauntz put it plainly: “When you say ‘Antigravity’ then the first thing that comes to mind is ‘yet another IDE’ and I have no desire in switching my IDE.” Another commenter noted that Anthropic manages to keep “Claude” as a unifying brand across their entire product line, while Google seems determined to fragment its own identity.
The Angular ghost
This pattern should feel familiar to anyone who’s watched Google’s relationship with open source over the years. Angular was open-source first, then rewritten as Angular 2 with a breaking migration that alienated the community. Google I/O 2026’s announcement of Antigravity alongside Gemini 3.5 Flash suggests the broader strategy is clear: Google’s building a platform, not a tool. Platforms are sticky. Tools are replaceable.
From a business perspective, it makes sense. From a community trust perspective, it’s another brick in the “Google abandons what you build on” wall.
What this means for the coding agent landscape
Gemini CLI was positioned as Google’s answer to Claude Code — a CLI-based coding agent you could run headless, pipe into workflows, and integrate into CI/CD pipelines. Antigravity CLI is being positioned in the same space, but the server-side harness requirement means it’s no longer a standalone tool. It’s a client to a platform.
For developers who built workflows around Gemini CLI’s open-source nature — custom extensions, local model integrations, forks with modified behaviour — June 18 is a hard deadline. The GitHub repository will presumably remain as an archive, but the live service disappears.
The GitHub discussion thread (#27274) has 61 comments and 74 replies. The tone ranges from resigned to furious. One maintainer’s attempt to reassure the community (“we made sure Antigravity CLI keeps the most critical features”) reads like a product manager’s response to a community that’s already left the chat.
The wider implication
What I find most interesting about this isn’t the tool itself — it’s the signal it sends about where Big Tech is heading with developer-facing AI. The pattern is consistent: ship something open to build community and gather usage data, then consolidate into a proprietary platform once adoption is proven.
Google is far from alone. Every major player is building walled gardens around their AI tools. The difference is that Gemini CLI was actually open-source with an active contributor base. When that gets folded into a closed platform, it’s harder to dismiss as “just a beta” or “experimental.” It was real, it was good, and it’s going away.
Seventeen days. If you’re using Gemini CLI, now is the time to decide whether Antigravity CLI meets your needs — or whether it’s time to look at what else is out there.
Sources:
– Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI (Dmitry Lyalin & Taylor Mullen, May 19, 2026)
– Hacker News: Gemini CLI will stop working from June 18, 2026 (406 points, 210 comments)
– GitHub Discussion #27274 (61 comments, 74 replies)
– The New Stack: Google pushes Pro, Ultra, and free users from open-source Gemini CLI to closed-source Antigravity CLI (Meredith Shubel, May 26, 2026)
