Gemini CLI Is Gone. Google's Replacement Is Antigravity CLI, and It's Not Open Source.

Gemini CLI stopped serving requests for Google AI Pro and Ultra users on June 18, 2026. Free tier users lost access at the same time. If you had Gemini CLI installed and have been relying on it, it’s no longer working today.

The replacement is Antigravity CLI.

Google made Antigravity available on May 19 at Google I/O and gave individual users about a month to migrate. That window closed today. Enterprise customers with paid Gemini Code Assist Standard or Enterprise licenses are unaffected — their CLI access continues as before.

What Antigravity CLI Is

Antigravity CLI is built in Go. Google says it’s faster than Gemini CLI at startup and execution, which tracks given Go’s lightweight runtime. The bigger pitch is multi-agent orchestration: instead of a single synchronous conversation, you can kick off several background tasks — a refactor here, a research pass there — without waiting for each to finish before starting the next.

The core features from Gemini CLI carried over. Agent Skills, Hooks, Subagents, and Extensions (now renamed Antigravity plugins) are all present. Configuration syntax and project files will need to be updated during migration, but the conceptual model is similar.

Antigravity CLI also ties into Antigravity 2.0, the redesigned desktop app Google relaunched at I/O. They share the same plugin architecture, so a plugin built for the CLI works in the desktop app as well.

The Open-Source Problem

Gemini CLI was Apache 2.0 licensed. Developers could read the source, fork it, audit it, or build on top of it. Antigravity CLI has no equivalent open-source release. Google hasn’t committed to publishing the source.

That’s a meaningful change. For teams that use Gemini CLI in regulated environments, auditing the tool was part of the approval process. For individual developers, an open source CLI is just easier to trust. The shift to a closed binary is the part of this transition generating the most friction in developer communities.

Google hasn’t addressed this directly. The migration documentation focuses on feature parity and performance, not the licensing change.

Who This Affects

The enterprise exception is important to understand. If your organization pays for Gemini Code Assist Standard or Enterprise through Google Cloud, you’re not migrating today. Google explicitly carves out that path. CLI access continues with model updates included.

What stops working today is the consumer-facing use case: individual developers using Google AI Pro or Ultra subscriptions, free-tier users who got Gemini CLI access as part of Google AI Studio access, and anyone who installed Gemini CLI without tying it to a Google Cloud project.

GitHub extension installations for Gemini Code Assist also stopped accepting new installs as of today.

Migration

Google’s migration documentation points developers to the Antigravity CLI setup guide. The CLI is available now. For existing Gemini CLI users, the main steps are reinstalling via the Antigravity package, updating configuration files to the new format, and remapping any extensions to the Antigravity plugin system.

Google has scheduled video walkthroughs and a community forum for questions. The technical preview has been available since May 19, so there’s already a month’s worth of community experience with the new tool.

The broader Antigravity 2.0 platform — desktop app, CLI, public SDK, and hosted agents — is Google’s bet on what a coding assistant looks like when tasks are measured in minutes and hours, not individual completions. Whether that’s a good direction or a corporate land-grab on open developer tooling is a reasonable debate. Today it’s simply the new reality: Gemini CLI is off, and Antigravity CLI is what’s there.

Sources: Google Developers Blog, June 2026, The Register