Google has decided to phase out Gemini CLI for most individual users and steer them toward Antigravity CLI, a new closed-source tool tied to their proprietary development platform. The decision has sparked a strong reaction among developers because it’s not just about any product: Gemini CLI was an open-source project, licensed under Apache 2.0, with over 100,000 GitHub stars, 6,000 merged pull requests, and hundreds of contributors.
The deadline highlights the issue. Google announced the transition on May 19, and Gemini CLI will stop serving requests on June 18, 2026, for free users, Google AI Pro, Ultra, and individual Gemini Code Assist users. Practically, it’s less than a month to abandon a tool many had integrated into their workflows. Enterprise clients with Gemini Code Assist Standard or Enterprise won’t face the same cut: Google states their access remains unchanged.
The code remains open, but the service is shutting down
The tension arises from a nuance that’s often overlooked. The Gemini CLI code can still be available under a permissive license. This allows use, study, modification, or forking. But Gemini CLI was more than just code: it was an interface to Google’s models, a component that depended on servers, authentication, quotas, APIs, and infrastructure outside community control.
That’s the crux. In a traditional open-source project, if a company changes direction, the community can fork the code and continue. This has happened many times: licenses tighten, companies retreat, or providers decide to shut parts of their product, resulting in community-maintained forks. With Gemini CLI, this exit strategy exists only partially. You can keep the steering wheel, but not the engine.
Google argues that user workflows have changed, and now there’s a need for multi-agent tools, unified backend, and a more integrated experience with Antigravity. The company claims that Antigravity CLI retains critical features like Agent Skills, Hooks, Subagents, and Extensions—now implemented as plugins—though fully parity from day one isn’t guaranteed.
That distinction matters. It’s not just a name change. For many developers, it means shifting from an open, auditable tool developed with community input to a proprietary alternative still in development. The Register notes that while the Gemini CLI repository contains the project code, the public Antigravity CLI page offers basic documentation, a changelog, and a demo but no equivalent open-source code.
Community contributed value but loses control now
The discontent isn’t only due to the closing date; it stems from collective investment. Gemini CLI didn’t grow solely thanks to Google—developers reported bugs, proposed improvements, built extensions, tested edge cases, and helped turn an experimental tool into part of their daily infrastructure.
This changes the nature of the debate. When a company releases a proprietary product and then withdraws it, it can be frustrating but predictable. When it invites community contributions to an open project, merges thousands of pulls, and then shifts the core development into a closed environment, perceptions shift. The license protects the code but not the time, trust, or expertise contributed by the community.
Google hasn’t deleted the repository nor changed the Gemini CLI license. That must be acknowledged. Technically, the code remains available. But the main value of the tool depended on a service Google can restrict, redirect, or limit to paying customers. For individual users and contributors, the message is unwelcome: they helped improve a tool that now may no longer serve them under the same conditions.
This decision also fuels a pattern that weighs on Google’s reputation. The website Killed by Google documents hundreds of discontinued products over the years. Not all closures are comparable or equally serious, but in development tools—a space where habits, automations, and processes are built—the memory persists.
Open source in the AI era: a new dependency
The Gemini CLI case highlights a broader issue with open source in artificial intelligence. For decades, releasing the code of a tool offered the community a real path for continuity. In generative AI, that guarantee can be fragile if the open project depends on closed models, private APIs, or centralized infrastructure.
A library, editor, or framework can survive after its original company withdraws. But an AI client that functions only when connected to proprietary models is far more vulnerable. Open-source code may be important but isn’t necessarily sufficient on its own.
This prompts technical teams to ask tougher questions before deploying AI tools in production: Does it work with multiple providers? Can it switch models without rebuilding everything? Can the provider cut off access on short notice? Are local or open weights options available? Does the project have independent governance, or is it wholly dependent on a single company’s decisions?
Antigravity could become a valuable tool, potentially improving performance, multi-agent coordination, and integrated experience compared to Gemini CLI. But that’s not the only concern. The real issue is whether Google managed the transition well, considering the community’s contribution to the original tool. Many developers feel the answer is negative.
The real risk: loss of influence
The lesson isn’t just that Google discontinues products. It’s that contributing to a large company’s open-source project doesn’t necessarily grant influence over its future. You might access the code, contribute improvements, and gain visibility, but strategic control remains with the platform owner—especially when much of the value relies on proprietary services.
This doesn’t mean developers should refuse all corporate open-source tools; many have been crucial to the industry. It does mean distinguishing between open code, open governance, and operational dependence. They are three separate things.
Gemini CLI’s code was open, but its practical continuity depended on Google. When Google decided to focus efforts on Antigravity CLI, the community saw the real limits of their influence. Legally, the repository remained intact; socially and strategically, trust was affected.
For companies, the message is clear: if an AI tool is part of your daily workflow, just checking the license isn’t enough. You need to understand who controls access, models, quotas, roadmap, and what happens if the product disappears. In the era of agents, influence isn’t just in the repository—it’s in everything that happens behind the scenes.
Frequently Asked Questions
What will happen to Gemini CLI on June 18, 2026?
Google will stop serving requests for Gemini CLI and Gemini Code Assist IDE extensions to free users, Google AI Pro, Ultra, and individual Gemini Code Assist users.
Does Gemini CLI stop being open source?
No. The repository remains available under Apache 2.0 license. The issue is that practical access to the service changes for many users because it depended on Google’s models and infrastructure.
What is Antigravity CLI?
It’s the new command-line tool integrated into Google’s Antigravity platform, designed for multi-agent workflows and sharing backend with Antigravity 2.0.
Why has this upset the community so much?
Because Gemini CLI received thousands of contributions from external developers, and now individual users must migrate to a tool that, for now, doesn’t offer the same degree of openness or feature parity.