by Michael Joiner

Gemini CLI Stops Working June 18. Here's How to Switch to Antigravity CLI.

Google is pulling the plug on Gemini CLI for consumer users on June 18, 2026. The replacement is Antigravity CLI — a Go-based, multi-agent tool that's available now. Enterprise licenses are unaffected.

Share

If you use Gemini CLI, you have five days. On June 18, 2026, Google stops serving requests through Gemini CLI for all consumer tiers — including Google AI Pro, AI Ultra, and the free tier. After that date, gemini commands simply won’t work.

Gemini CLI transitioning to Antigravity CLI — official Google announcement graphic
Source: Google Developers Blog

Google announced the transition on May 19. The replacement is Antigravity CLI, a new tool built in Go that Google describes as its “premier agent-first development platform.” It’s been available since the announcement.

Who’s Affected

Consumer users are the ones who need to migrate:

  • Google AI Pro subscribers
  • Google AI Ultra subscribers
  • Free tier Gemini CLI users
  • GitHub organization users running Gemini CLI without an enterprise license

Enterprise users with a Gemini Code Assist Standard or Enterprise license are unaffected. Their access continues and Google is keeping those licenses maintained.

What Changes With Antigravity CLI

The new tool keeps the features that developers built workflows around: Agent Skills, Hooks, Subagents, and Extensions (now called Antigravity plugins). The core mental model carries over.

What’s different:

  • Built in Go: Antigravity CLI runs as a Go binary (agy), compared to Gemini CLI’s Node.js-based approach. Google says this makes it faster.
  • Async multi-agent workflows: You can run multiple agents in the background simultaneously. In Gemini CLI, starting a long-running task locked your terminal session. Antigravity CLI lets you queue background work and keep your terminal free.
  • Shared architecture with Antigravity 2.0: The CLI and the desktop app now share the same underlying platform, so features developed for one tend to land in the other.

The migration is not completely seamless. The developer community had concerns in the GitHub discussion: Antigravity CLI moves away from OAuth authentication in some configurations, some Gemini CLI features don’t have direct equivalents yet, and the new tool is closed-source where Gemini CLI was Apache 2.0 licensed.

How to Migrate

Antigravity CLI is available now at antigravity.dev. Google released migration documentation and video walkthroughs alongside the announcement. The basic steps:

  1. Install Antigravity CLI (agy)
  2. Authenticate with your Google account
  3. Map your existing Agent Skills and Extensions to Antigravity plugins
  4. Update any scripts or aliases that invoke gemini to use agy

If you’ve built Hooks or Subagents, those should transfer with minimal changes since the concepts carry over directly.

Why the Switch

Google framed the transition as a consolidation move. Running two separate CLI tools — Gemini CLI and Antigravity CLI — on diverging architectures creates maintenance overhead and feature lag. Unifying them into Antigravity lets Google ship improvements once and have them land everywhere.

The timing aligns with Google’s broader push behind the Antigravity platform, which launched the Antigravity 2.0 desktop app and has been positioning itself as Google’s primary developer AI product.

Sources

Share

The Weekly Diff

One email a week: every AI coding tool price change, plan restructure, and major release we verified, with sources. No filler.

Free. Unsubscribe anytime.