Google Accepted 6,000 Gemini CLI Contributions, Then Closed Tool for Enterprise Only

Google spent nearly a year accepting code contributions from hundreds of independent developers on an open-source AI terminal tool — then on May 19, 2026, announced it would withdraw API access from all non-paying users and hand the project's future exclusively to enterprise customers, while replacing it with a closed-source successor that, by Google's own admission, does not yet match it feature for feature.

The tool is Gemini CLI, a TypeScript-based AI coding agent released under the Apache 2.0 license in June 2025. Over the following year it accumulated over 100,000 GitHub stars and more than 6,000 merged pull requests from external contributors — a level of community investment that Google's own announcement cited as evidence of the project's success. On June 18, 2026, Google will stop serving requests for free users, Google AI Pro and Ultra subscribers, and individual Gemini Code Assist users. Enterprise customers with paid Gemini Code Assist Standard or Enterprise licenses are explicitly exempted: they keep Gemini CLI, keep model updates, and keep security patches.

The community that supplied the labor does not.

Developers Name the Pattern

The response in Google's GitHub discussion thread announcing the transition was immediate and pointed. Developer Andrea Alberti, who had a 27-commit pull request merged the same day as the announcement, asked directly whether community contributors had "essentially working for free on a code base that will only be used in enterprises." GitHub user N1kky-wed wrote that the move sent "a pretty discouraging message for contributors." Another commenter, secretnarwhal, summarized the community's read: "So, basically, we're making the project closed source. That's it."

Christine Hall, a journalist at FOSS Force who has covered open source since 2002, published an analysis on May 22 calling it "a new twist on a game that's become increasingly common in recent years." Her assessment: Google's move effectively removed only the open-source part of the equation — not by switching the license, but by switching off the infrastructure that made the tool useful to anyone who wasn't paying. The sunsetting of Gemini CLI, she noted, "only affects open source users. It doesn't happen for those who pay for the product."

The pattern has a name in the developer community. Contributors on the Gemini CLI repository and across Hacker News threads are calling it a bait and switch: open-source release to attract labor, community builds the product, enterprise captures the value, community gets a closed replacement.

What Apache 2.0 Does and Does Not Protect

The Gemini CLI GitHub repository remains publicly accessible. The Apache 2.0 license is intact. But an open-source license governs code — it says nothing about API access, model quotas, authentication systems, or the cloud infrastructure that determines whether the code actually runs.

Google's own Antigravity CLI GitHub repository, introduced as the replacement, contains a changelog, a readme, and a demonstration GIF. There is no source code. The Register confirmed that developers noticed the absence within hours of the announcement.

Group product manager Dmitry Lyalin acknowledged in his GitHub post that the Gemini CLI repository "remains available to the community as an Apache 2.0 licensed repository with no changes." What he did not address is that without a Google backend serving requests, the codebase becomes an archive. Running a working fork would require independent access to a compatible large language model — a non-trivial engineering undertaking that effectively ends community use of the tool as a practical matter.

Replacement Ships Incomplete, with Tighter Quotas

Google announced at Google I/O 2026 that Antigravity CLI was "available to everyone" starting May 19. In practice, the agy binary — the new CLI command — was not available on npm or Homebrew as a named package as of May 21. Google's own announcement acknowledged that Antigravity CLI "won't have 1:1 feature parity right out of the gate."

Usage limits are also drawing complaints. Multiple users on the Antigravity CLI issues tracker reported exhausting their weekly quota within a small number of requests — a downgrade from Gemini CLI's previous 1,000-request daily free tier. Antigravity CLI's quota refreshes weekly, not daily, and several users reported hitting it within roughly 2,000 lines of generated code.

Launch partners including Dynatrace, Elastic, Figma, Shopify, and Stripe had built integrations into the Gemini CLI ecosystem. Those integrations now face disruption within a four-week window. Developers who embedded Gemini CLI invocations in CI/CD pipelines, GitHub Actions workflows, or Docker containers face binary-name changes and configuration rewrites with no extended runway.

Google's Stated Rationale

Lyalin and Taylor Mullen, Google's principal engineer on the project, framed the transition as an architectural necessity. "You now require multiple agents communicating with each other to split up the work and solve complex problems," they wrote in the May 19 announcement. "This means your terminal tools need to share a unified backend with the rest of your workflow."

Antigravity CLI is built in Go rather than TypeScript, which Google says makes it faster. It supports asynchronous multi-agent workflows that run in the background without blocking the terminal, and shares an underlying architecture with the Antigravity 2.0 desktop application. Google has published migration documentation and promised video walkthroughs in the coming weeks.

The "single platform" argument would be more persuasive, critics note, if it applied to everyone. It does not: the enterprise tier retains Gemini CLI alongside Antigravity CLI access. The consolidation Google describes as a technical imperative for free users is, for paying enterprise customers, optional.

What Developers Should Do Before June 18

Developers relying on Gemini CLI on any non-enterprise tier have until June 18 to migrate. Google's migration documentation is available via the Antigravity platform. Developers unwilling to move to closed-source tooling are evaluating Claude Code, GitHub Copilot's CLI integrations, and open-source alternatives built on locally hosted models — each with its own cost structure and workflow requirements.

The episode is already reshaping how developers evaluate corporate-backed open-source projects. The lesson a number of contributors are drawing publicly: a permissive license on the code is not a guarantee of continued access to the service that makes the code run. In an era when AI developer tools depend on cloud backends, model APIs, and vendor-controlled quotas, the meaningful question is not who owns the repository — it is who controls the infrastructure.

Google did not respond to questions from The Register prior to that publication's story on May 20.