Google Replaces Open-Source Gemini CLI with Closed-Source Antigravity CLI, Frustrating Developers
Key Takeaways
- ▸Gemini CLI (open-source) is being deprecated on June 18, 2026, and replaced with Antigravity CLI (closed-source), except for enterprise users with paid Gemini Enterprise Agent Platform API keys
- ▸Antigravity CLI lacks feature parity with Gemini CLI at launch and users report hitting weekly usage quotas with just a few requests
- ▸The transition from open-source to closed-source has sparked developer backlash on GitHub, with concerns about transparency, usage limits, and Google's decision to commercialize an open-source tool
Summary
Google announced at its I/O conference that it will deprecate Gemini CLI (open-source) on June 18, 2026, replacing it with the newly launched Antigravity CLI (closed-source). The change affects free users, Google AI Pro and Ultra subscribers, and GitHub users, though enterprise customers with paid API keys will retain access to Gemini CLI. Developers have expressed frustration on GitHub over the closed-source nature of Antigravity CLI, lack of feature parity, and reported strict usage limits.
While Google positions Antigravity CLI as offering improved multi-agent support and unifying its CLI development efforts, the new tool does not achieve feature parity with its predecessor at launch. Some features like agent skills, hooks, subagents, and extensions are supported, but others may take time to arrive, if at all. The shift from open-source to closed-source represents a significant departure from Gemini CLI's Apache 2.0 licensed model, and community members have raised concerns about Google leveraging open-source contributions to build a closed product while imposing strict usage quotas.
- Enterprise customers are unaffected by the change and will continue to access Gemini CLI through paid API keys
Editorial Opinion
Google's decision to deprecate the open-source Gemini CLI in favor of a closed-source Antigravity CLI reflects a troubling trend of commercializing community-driven tools. While improved multi-agent support is valuable, the lack of transparency around source code, feature parity gaps, and aggressive usage quotas suggest the company is prioritizing profit over developer experience. This move risks alienating the developer community and may accelerate adoption of open-source alternatives from competitors.
