Google Developers Blog Google Is Sunsetting Gemini CLI for Consumer Users on June 18
Google announced at I/O 2026 that Gemini CLI will stop serving requests for free and Pro/Ultra users on June 18. Consumer users must migrate to Antigravity CLI. Enterprise and API-key users are not affected.
Google announced at I/O 2026 this week that Gemini CLI is being folded into Antigravity CLI. For developers using Gemini CLI through a free account or a Google AI Pro/Ultra subscription, the cutover date is June 18, 2026. After that, Gemini CLI stops serving requests for those tiers.
The announcement on the Google Developers Blog frames the transition as a consolidation rather than a shutdown. Antigravity CLI is already available to all users as of May 19.
Who needs to act
If you access Gemini CLI through a free tier or a Google AI Pro or Ultra subscription, you have until June 18 to switch to Antigravity CLI.
Enterprise customers are not in the same position. Organizations using Gemini CLI through a Gemini Code Assist Standard or Enterprise license retain full access without needing to migrate. The same applies to organizations using Gemini Code Assist for GitHub via Google Cloud. API-key users also keep access.
Gemini Code Assist for GitHub will stop accepting new installations on June 18, but existing requests will continue to be served for a few more weeks after the cutover date.
What changes in Antigravity CLI
The core workflow carries over. Antigravity CLI retains Agent Skills, Hooks, Subagents, and Extensions — the last of those renamed to Antigravity plugins. The command set and configuration patterns that Gemini CLI users are familiar with are preserved.
The new CLI is built in Go rather than TypeScript/Node.js, which Google says makes it faster and more responsive. It also shares the same agent harness as the Antigravity 2.0 desktop application, so improvements to the underlying agent runtime apply across all surfaces automatically.
The stated reason for the consolidation is architectural. Gemini CLI was built for single-agent terminal tasks. Antigravity CLI is designed to orchestrate multiple agents running asynchronously in the background, which is the direction Google has pushed since the I/O 2026 announcement of Antigravity 2.0. Having two separate tools with two separate backends makes that harder to build.
What to do
Migration documentation is available from Google, along with upcoming video walkthroughs. Feedback can be submitted in the Antigravity CLI GitHub forum.
The June 18 deadline is about a month away. For most users, the migration is a tool swap rather than a workflow rewrite — the key capabilities come with you.
Source: Google Developers Blog, GitHub discussion