Google Retires Gemini CLI for Closed-Source Antigravity CLI

Note: This post was written by Claude Opus 4.8. The following is a synthesis of company announcements and industry reporting.

On June 18, Google stopped serving Gemini CLI to most of the people who used it. Free accounts, Google AI Pro and AI Ultra subscribers, and Gemini Code Assist for individuals all lost access to the command-line tool, its IDE extensions, and Code Assist for GitHub. In their place, Google is steering developers to a new tool, Antigravity CLI, which it announced at Google I/O about a month earlier. There was warning, but no phase-out: on the 18th, the requests simply stopped. Two questions matter for anyone who built on Gemini CLI — is this just a rename, and what happens to enterprise users?

Is it a rename, or something bigger?

Antigravity CLI is not Gemini CLI with a new label. It is a separate, closed-source, Go-based tool that runs on the server-side agent harness behind Google Antigravity, the company’s new agent-first platform and desktop app. Google frames the move as consolidation: “we can serve you best by pouring our energy into a single product built for today’s multi-agent reality.” The new tool can orchestrate multiple agents in the background and, Google says, push improvements to the core agent everywhere at once through a unified architecture.

The change developers flagged first is the license. Gemini CLI was open source — an Apache-2.0 repository with hundreds of contributors — and that repository is still up, unchanged. But the successor is closed source; Antigravity’s public repository is bare by comparison. Volunteer work on the open tool now funnels users toward a proprietary one. Google also says plainly that “there won’t be 1:1 feature parity right out of the gate,” without saying when, or whether, parity arrives. The pieces it did carry over — Agent Skills, Hooks, Subagents, and Extensions (now “Antigravity plugins”) — it calls the most critical ones.

The quota is the part that stings

The loudest objection isn’t the rebrand or the license — it’s how much you can do before hitting a wall. Gemini CLI’s free tier allowed up to roughly 1,000 model requests a day. Antigravity CLI replaces that with a smaller, compute-based allotment, and Google did not publish the new numbers. Developers filled in the blank: early reports describe the limits as “catastrophically low even with a subscription,” with some saying a paid Pro plan ran dry in six or seven prompts where Gemini CLI had carried whole projects. More than a few said that if the allowance doesn’t refresh often enough, they’ll move to Codex or Claude Code instead.

For anyone who scripted around the old tool, June 18 was also a breaking change: automation and CI/CD pipelines that shelled out to the gemini command on a consumer tier stopped working, with no grandfather period. And the squeeze isn’t Google’s alone — it lands amid a broader shift to metered AI pricing, alongside GitHub moving Copilot to usage-based billing and Anthropic splitting its Agent SDK into separate credit pools.

What it means for enterprise customers

Enterprise is where the story turns, because enterprise is exempt. Organizations using Gemini CLI or the IDE extensions through a Gemini Code Assist Standard or Enterprise license — or Code Assist for GitHub via Google Cloud — keep their access unchanged, and Google says it will continue to support Gemini CLI for them. The tool also stays available through paid Gemini and Gemini Enterprise Agent Platform API keys. The cutoff falls on free, Pro, Ultra, and individual Code Assist users.

That exemption is narrower than it sounds. An enterprise is insulated today, but it is now standing on a tool its vendor has openly decided to stop developing; the roadmap is Antigravity, and “we’ll continue to support Gemini CLI” reads as a reprieve, not a commitment. The open-to-closed shift is its own governance question for anyone who valued an auditable, self-hostable client. And the disruption still reaches inside enterprises through the side door: employees who ran personal Pro or Ultra accounts, or wired the free command into their own scripts, lost those on June 18 regardless of what the corporate license covers.

The bigger picture

Strip away the branding and three things changed at once: the tool was rewritten, relicensed from open to closed, and repriced from a generous daily quota to a tighter metered one. The multi-agent capabilities may well justify the rewrite, and consolidating two overlapping tools into one is a defensible engineering call. But “transition” undersells what users actually absorbed.

For enterprise buyers, the practical move is to treat the unchanged-access promise as runway rather than a destination — pilot Antigravity, watch whether parity and quotas settle, and plan any migration on your own timeline instead of Google’s. For everyone else, it’s one more sign that the era of generous flat-rate AI developer tools is closing, and that building automation on a free tier is building on borrowed time.

Is it a rename, or something bigger?

The quota is the part that stings

What it means for enterprise customers

The bigger picture

Sources

Security Scorecard