On May 19th, Google published what it called “a significant update.” By June 18th, Gemini CLI — open source, Apache 2 licensed, with over 100,000 GitHub stars and more than 6,000 merged pull requests from hundreds of contributors — will stop serving requests for the vast majority of users. The replacement? Antigravity CLI: a closed-source binary in Go with a GitHub repo that contains a README, a changelog, and an animated GIF. No source code.
I’ve been covering developer tooling long enough to recognize a pattern. This isn’t a product transition. It’s a withdrawal of trust.
What Really Happened
Google framed the closure as evolution. The official blog post talks about “multi-agent reality,” “unified architecture,” and “a single platform built for today.” The argument is that Gemini CLI proved the concept, and now Antigravity CLI is the mature version — faster (built in Go), with async support, and sharing the same backend as Antigravity 2.0 desktop.
That’s the marketing version. Here’s what’s actually happening:
A tool that the developer community built — with real pull requests, real forks, real issue tracking — is being retired in favor of a 140 MB closed-source binary. Simon Willison, one of the most respected voices in the open source AI tooling space, said it plainly in the Hacker News thread: Gemini CLI was Apache 2 licensed with a public repo. The Antigravity CLI repo has a README and an animated demo GIF.
An HN user who reverse-engineered the binary documented what’s inside: a Chrome DevTools Protocol / Playwright client, a macOS Seatbelt sandbox, Sentry for crash reporting, Unleash for feature flags, embedded Go-git, and its own language detector. A closed 140 MB black box with its own browser control stack. Not exactly a minimalist CLI.
Who Gets Cut Off on June 18th
The cutoff isn’t uniform, which makes the picture worse:
- Free users (Gemini Code Assist for individuals): no access as of June 18th
- Google AI Pro and Ultra subscribers: no access as of June 18th
- Gemini Code Assist for GitHub (free tier): no new installations as of June 18th, requests stop processing shortly after
Who keeps access? Enterprise customers with Gemini Code Assist Standard or Enterprise licenses, and those using paid Gemini API keys. In other words: if you were using this tool for free — even if you were one of the hundreds of contributors who helped build it — you’re out.
The forced upgrade to Antigravity 2.0 adds another problem: users report that it deletes chat history and settings, and weekly quotas are exhausted after just a couple of requests. You’re migrated to the new product, and the new product barely works.
The Real Problem for Development Teams
Beyond the ideological debate about open source, there are practical consequences for teams in Latin America:
No auditability. With Gemini CLI, you could inspect the code, understand exactly what was being sent to Google’s servers, fork it and modify it. With a closed binary, you have to trust Google. For teams with data sovereignty requirements, or those working with sensitive codebases, this isn’t a theoretical concern — it’s a compliance question.
No community extensions. The open source model enabled a real ecosystem of forks and extensions. That ends with a closed binary. You get what Google decides to ship.
Harder-to-reverse vendor lock-in. An open source tool can be forked if Google abandons it. A closed binary can’t. The risk profile of depending on Antigravity CLI is categorically different from depending on Gemini CLI.
Time pressure. June 18th is less than 30 days away. Teams that have automated workflows, scripts, or CI/CD pipelines built on Gemini CLI need to act now.
What I’d Recommend
If you’re an enterprise customer: don’t rush. Your access doesn’t change and Google is under pressure to make this transition smooth. Evaluate Antigravity CLI carefully before committing workflows to it. A Googler mentioned in the HN thread that there’s a possibility Antigravity might eventually be open sourced — I’d wait to see if that materializes before betting your architecture on it.
If you’re on a free or Pro/Ultra plan: you need to migrate before June 18th or find alternatives. The obvious candidates are Claude Code and GitHub Copilot’s agent mode — both invested heavily in agentic workflows from the terminal. Codex CLI is another option. None are open source in the same way Gemini CLI was, but at least the transition is a deliberate choice rather than a forced one.
If you’re an open source contributor who sent pull requests to Gemini CLI: the code you contributed remains alive at github.com/google-gemini/gemini-cli under Apache 2. It can be forked. Someone in the community will probably do it.
The Pattern Underneath
Google has done this before — shutting down products that developers depend on — but this move stings particularly because of the open source component. The community built something real on the basis of Google’s commitment. Hundreds of people contributed code. And now Google is walking away from that deal, unilaterally, with 30 days’ notice.
There’s a comment from a Googler in the HN thread suggesting that Antigravity could eventually be open sourced. Maybe. But “we might open it eventually” isn’t the same as the Apache 2 license that existed last week.
The lesson for teams evaluating any open source tool backed by a hyperscaler: an open source license is only as durable as the company’s commitment to it. When the internal roadmap changes, the license doesn’t protect you from abandonment.
Once trust is withdrawn, it’s expensive to rebuild.