Google Ends Support for Open-Source Coding Tool, Forces Migration to New Closed-Source Option
On May 19, Google did something unusual for a company with Google-scale brand recognition: it killed a popular open source tool and replaced it with a closed-source equivalent, giving users thirty days to migrate.
The tool was Gemini CLI. The replacement is Antigravity CLI. And if you talk to developers about it, the reaction is roughly uniform: frustration laced with a specific kind of weariness that comes from watching this particular company do this particular thing one time too many.
Gemini CLI launched in 2025 as Google's terminal-native coding agent — a CLI that let developers invoke Gemini directly from the command line, scaffold projects, provision cloud infrastructure, and pipe results into CI pipelines. It accumulated over 100,000 GitHub stars and 6,000 merged pull requests from contributors who extended its capabilities, wired in their own MCP servers, and built workflows around its open API surface. It was Apache 2.0 licensed. You could read the source. You could fork it. Google Developers Blog
On June 18, that ends. Google announced at I/O 2026 that Gemini CLI will stop serving requests for AI Pro, AI Ultra, and free-tier users on that date. The replacement, Antigravity CLI, is a Go binary that shares the same agent harness as Antigravity 2.0, Google's new desktop IDE. The TypeScript codebase the open source community built on — the commits, the contributors — is replaced by a Go binary the community cannot read or fork. Google Developers Blog
Simon Willison noted something curious on his blog the day after I/O: the open source Gemini CLI runs on its own harness; Antigravity CLI runs on the same backend that powers Antigravity 2.0 and, notably, Gemini Spark — Google's consumer-facing AI agent that connects to Gmail, Drive, Calendar, and Docs. He flagged it as a FAQ item he wasn't sure warranted mentioning. The consolidation pattern is visible in the architecture. What it means strategically is still an open question. Simon Willison
The developer reaction on Hacker News drew 397 points and 203 comments and counting. Commenters called it a monkey knife fight and compared it to Microsoft circa 2010 publishing half a dozen media players that all did roughly the same thing and all got killed. One commenter asked whether Gemini carries more brand recognition for Google than Antigravity does. Hacker News
There is something structurally significant beyond the frustration, though. Google's stated rationale for the kill — that developers now need multiple agents working together and a shared backend is the right response — is coherent. A unified harness means improvements to core agent capabilities propagate to CLI and desktop simultaneously. The company's blog post frames this as listening to users and delivering what they actually need. Google Antigravity Blog
The counter is also coherent: Google has a pattern of killing developer-facing products (Reader, Stadia, Hangouts, the list goes back years), and this one comes with a forced migration on a deadline. Antigravity CLI is in public preview. Augment Code, which ran both tools against a 450,000-file monorepo, noted that Antigravity has "a publicly reported RCE issue" as of April 30 and no documented compliance certifications — unlike Gemini CLI's enterprise tier, which inherits Google Cloud's DPA framework. For enterprise teams being pushed off the open source CLI onto the new product, the security and compliance posture is a genuine open question, not marketing. Augment Code
The open source community could, in principle, fork Gemini CLI and keep it alive. The Apache 2.0 license permits it. Whether that fork survives without access to Google's latest models is a different question — the API endpoint that Gemini CLI hits is Google's, and that endpoint is what Google is turning off on June 18.
What exactly changes on June 18 is concrete: Gemini CLI users lose API access to Google's latest models through that interface. Antigravity CLI offers a Go binary install (no source to read, distributed via Google's own install script) and shares the same agent backend as Antigravity 2.0 — which is also what powers Gemini Spark, Google's consumer AI agent with access to Gmail, Drive, Calendar, and Docs. I could not confirm from the public GitHub repository whether source code is available for Antigravity CLI; the repository contains only README, changelog, and a demo GIF, with installation via Google's binary installer rather than a source build. For enterprise teams, the compliance picture is also unsettled: Augment Code noted Antigravity has "a publicly reported RCE issue" as of April 30 with no documented compliance certifications, while Gemini CLI's enterprise tier inherits Google Cloud's DPA framework — meaning the team being pushed off open source onto the new product may also be losing documented compliance guarantees in the migration. Augment Code GitHub