Google replaces Gemini CLI with Antigravity CLI

According to Google's public documentation and a GitHub announcement, Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro, Google AI Ultra, and users of the free individual tier on June 18, 2026 (Google Cloud release notes; GitHub announcement by Dmitry Lyalin). The GitHub post and Google Cloud docs instruct affected users to migrate to the new Antigravity CLI, which Google is distributing as the unified agent-first command line experience (GitHub announcement; Google Cloud documentation). The maintainers note that enterprises using Gemini Code Assist Standard or Enterprise, or accessing Gemini CLI via Google Cloud, will keep their existing access, and that Gemini CLI will remain accessible via paid Gemini and Gemini Enterprise Agent Platform API keys (GitHub announcement; Google Cloud docs). Public coverage by The Register reports that Antigravity CLI is not available as an open-source repository in the same way Gemini CLI was, and that the replacement has provoked community pushback (The Register).

Per the GitHub announcement, Antigravity CLI is written in Go, is designed to support asynchronous background workflows for complex multi-agent tasks, and shares architecture with the new Antigravity 2.0 desktop app; the announcement lists retained capabilities such as Agent Skills, Hooks, Subagents, and Extensions (GitHub announcement). The GitHub post also says the team will continue maintaining the Gemini CLI Apache 2.0 repository for enterprise customers with model updates, bug fixes, and security patches (GitHub announcement).

Editorial analysis - technical context: Developers who rely on local, reproducible CLI tooling typically value the ability to inspect, fork, and extend open-source clients. Moving a widely used CLI from an open-source project to a proprietary or closed distribution alters the available integration and audit pathways. For multi-agent workflows, the shift toward a platform designed for asynchronous orchestration can materially change runtime and deployment choices; practitioners will compare execution models, latency, local tooling support, and how agent skills map between the two CLIs.

Public reporting highlights immediate friction for individual and hobbyist users who previously accessed Gemini CLI at no cost. The transition is significant for developer experience rather than for model capability: it changes how developers run, extend, and troubleshoot agent workflows at the command line. Enterprises appear insulated by license or Google Cloud access, according to Google documentation and the GitHub announcement (Google Cloud docs; GitHub announcement). The Register frames the move as a reduction in openness for most users, which explains the visible community dissatisfaction (The Register).

For practitioners: The key operational impacts are practical. Developers who currently run long-lived local agents, custom extensions, or community-built plugins may need to evaluate compatibility and licensing; CI/CD pipelines that depend on the Gemini CLI endpoint for free tiers will need migration plans. Because the GitHub post warns that "there won't be 1:1 feature parity right out of the gate," teams should audit the exact feature set they depend on and test Antigravity CLI against critical workflows before the June 18 change (The Register; GitHub announcement).

• •Whether Google publishes an open-source repository or specification for Antigravity CLI, and the licensing terms if it does (The Register; GitHub announcement).
• •Release notes and migration guides that document missing features and timelines for parity between Gemini CLI and Antigravity CLI (Google Cloud release notes; developer docs).
• •Activity on the Gemini CLI GitHub repository and community forks, which will indicate whether the ecosystem preserves a self-hostable alternative (GitHub repository discussion).
• •Changes to pricing, quotas, or API-key requirements that affect individual developers and small teams (Google Cloud documentation).