Google announced at its I/O conference this week that it will discontinue the Gemini Command Line Interface (CLI) for most users on June 18, 2026, replacing it with Antigravity CLI, a closed-source alternative that developers say lacks transparency and imposes restrictive usage quotas. The move marks a significant shift away from open-source development practices and has sparked considerable backlash in the developer community.

What Is Happening to Gemini CLI?

The Gemini CLI, an open-source development tool that allows programmers to interact with Google's AI models from the command line, will stop serving requests for Google AI Pro and Ultra users, as well as those using the free tier of Gemini Code Assist for individuals on June 18. The tool will also affect Gemini Code Assist for GitHub, which will no longer allow new installations starting that date and will cease serving requests in the following weeks.

However, enterprise customers are getting a reprieve. Organizations using Gemini CLI or its integrated development environment extensions through Gemini Code Assist Standard or Enterprise licenses will retain full access without interruption. Similarly, developers accessing the tools through enterprise Google Cloud accounts will see no changes. Google also noted that Gemini CLI will remain accessible to anyone willing to pay for access via paid Gemini and Gemini Enterprise Agent Platform API keys.

Why Are Developers Upset About Antigravity CLI?

The replacement tool, Antigravity CLI, represents a fundamental departure from Google's previous approach. While the original Gemini CLI is fully open-source with all code publicly available on GitHub, Antigravity CLI's GitHub repository contains only a changelog, readme file, and a demonstration image. The absence of publicly available source code has alarmed developers who valued the transparency and community contributions that open-source projects enable.

Beyond the closed-source nature, developers report encountering aggressive usage limits. Multiple users have posted on GitHub that they hit their weekly quota after just a couple of requests, raising concerns about whether the tool will be practical for real-world development work. The issues page for Antigravity CLI is filled with complaints about these restrictions, with some developers accusing Google of leveraging open-source contributions to build a proprietary replacement.

What Features Are Missing From Antigravity CLI?

Google acknowledged that Antigravity CLI will not offer complete feature parity with Gemini CLI at launch. The company stated that "there won't be 1:1 feature parity right out of the gate" between the two tools. At launch, Antigravity CLI will support agent skills, hooks, subagents, and extensions, but other capabilities may take time to arrive, if they arrive at all.

Google

This incomplete feature set means developers switching to Antigravity CLI may lose access to functionality they currently rely on, with no guarantee those features will be restored in the future.

How to Maintain Access to Gemini CLI After June 18

• Enterprise Licensing: Organizations can maintain full access by upgrading to Gemini Code Assist Standard or Enterprise licenses, which are exempt from the discontinuation.
• Paid API Keys: Individual developers can continue using Gemini CLI by purchasing access through paid Gemini or Gemini Enterprise Agent Platform API keys, though this requires ongoing financial commitment.
• Self-Hosting Open-Source Version: The Gemini CLI remains available as an Apache 2.0 licensed open-source repository on GitHub, meaning developers can theoretically fork and maintain their own versions, though this requires technical expertise and ongoing maintenance.

Gemini CLI Lead Product Manager Dmitry Lyalin attempted to clarify the situation on GitHub, noting that "the project remains available to the community as an Apache 2.0 licensed repository with no changes" and that Google will continue updating it with the latest model releases and security fixes for enterprise customers. However, this statement only underscores the divide between enterprise and individual developers, as the open-source version will effectively become a second-class tool maintained primarily for paying customers.

What Does This Mean for Google's AI Development Strategy?

Google framed Antigravity CLI as a way to unify its command-line interface efforts and improve support for multi-agent environments, where multiple AI agents work together on complex tasks. The company positioned the transition as a natural evolution of its tooling strategy. However, the shift from open-source to closed-source, combined with usage restrictions and incomplete features, suggests Google is prioritizing control and monetization over community engagement.

The decision reflects a broader tension in the AI industry between open-source principles and proprietary business models. While Google has historically championed open-source AI research, this move signals a willingness to restrict access when it serves commercial interests. For developers who have invested time in learning Gemini CLI's open-source codebase, the forced migration represents a loss of autonomy and transparency.

The developer backlash on GitHub demonstrates that this strategy carries reputational costs. Many comments express frustration not just with the tool itself, but with Google's apparent willingness to use open-source contributions as a foundation for closed-source products. Whether Google will reconsider its approach or double down on the Antigravity CLI transition remains to be seen, but the June 18 deadline is now less than a month away.