Gemini CLI Stops Serving Requests Today: Google Forces the Move to Closed-Source Antigravity CLI

TL;DR

Starting today, June 18, 2026, Google's Gemini CLI and the Gemini Code Assist IDE extensions stop serving requests for Google AI Pro, Ultra, and everyone on the free tier. The replacement is Antigravity CLI, a Go-based, agent-first terminal tool that shares an engine with the Antigravity desktop app. The catch for this audience: the old Gemini CLI was open source under Apache 2.0, and Antigravity CLI is closed source. Google has openly said there is no 1:1 feature parity at launch. If you wired Gemini CLI into scripts, CI, or cron jobs, some of that breaks today. Enterprise and paid-API access is the exception.

What Actually Changed Today

Google announced the transition back on May 19, but today is the day the lights go out. Per Google's own developer blog, on June 18, 2026 Gemini CLI and the Gemini Code Assist IDE extensions stop serving requests for:

• Google AI Pro subscribers
• Google AI Ultra subscribers
• Anyone using Gemini Code Assist for individuals free of charge

For Gemini Code Assist for GitHub, there are no new installations on GitHub organizations as of today, and requests stop being served in the following weeks. This is not a deprecation warning. The binary on your machine keeps existing, but the backend stops answering it, which is the part that matters.

Who Keeps Access (The Fine Print)

Not everyone is cut off. Access continues, unchanged, if you fall into one of these buckets:

• Your org uses Gemini CLI or the IDE extensions under a Gemini Code Assist Standard or Enterprise license.
• Your org uses Gemini Code Assist for GitHub through Google Cloud.
• You are calling the models with a paid API key.

The pattern is blunt: if you were paying at the enterprise tier, you are fine. If you were on the free or prosumer tiers, today is a forced migration. The Register's read on it was sharp: the open-source tool effectively gets paywalled, kept alive only for enterprise customers while everyone else is pushed onto a closed product.

Why This Stings: Open to Closed

This is the part worth sitting with, because it is the real story for builders. Gemini CLI shipped as an open-source project on GitHub under the Apache 2.0 license. People filed issues, sent pull requests, and built extensions on top of it precisely because it was open and inspectable.

Antigravity CLI is closed source. The community reaction has not been quiet. The loudest criticism in the GitHub discussion and on Hacker News is that Google used open-source contributions to harden a tool, then rolled the good parts into a closed replacement and retired the open one. Whether or not you think that is fair, it is a pattern worth recognizing before you pour more free labor into a vendor's repo.

Open weights and open tools without a durable license guarantee are a loan, not a gift. The lender can call it back.

What Antigravity CLI Gives You In Return

To be fair to the new tool, it is not just a rebrand. The headline upgrades:

• Built in Go. The old CLI was a Node project. The rewrite in Go is reported to be snappier and more responsive, with a single compiled binary instead of a Node runtime dependency.
• Agent-first, async by design. Antigravity CLI orchestrates multiple agents in the background, so you can kick off a large refactor or parallel research task without locking up your terminal session.
• Shared engine with the desktop app. The CLI and the Antigravity desktop application run on the same underlying architecture, so behavior is meant to be consistent across both surfaces.

Critical Gemini CLI features carry over by name: Agent Skills, Hooks, Subagents, and Extensions (Extensions are now called Antigravity plugins). That is the good news. The bad news is Google's own caveat that there will not be 1:1 feature parity out of the gate, so do not assume your exact workflow maps cleanly on day one.

How To Migrate Without Losing a Day

The installer story is different from the old one. Gemini CLI was an npm install. Antigravity CLI is not distributed via npm. Instead you run a single OS-specific shell command, and the installer drops a compiled binary into a local bin directory (on Unix, your user-local bin path; on Windows, a local AppData location). Reports put the binary name as agy rather than something longer to type.

A sane migration checklist for today:

• Inventory every place you call Gemini CLI. Shell aliases, Makefiles, CI pipelines, git hooks, cron jobs. Anything that shells out to the old command is a candidate to break the moment the backend stops answering.
• Install Antigravity CLI from Google's official channel and confirm the new binary runs and authenticates against your account tier.
• Port your config. Move your Skills, Hooks, and Subagents over, and re-add Extensions as Antigravity plugins. Expect to fix at least one thing that does not map cleanly, given the no-parity warning.
• Re-test automation end to end. Do not trust that a script that worked yesterday works today. The command name, flags, and output format may differ.
• If you are an enterprise/API user, verify you are actually exempt before assuming nothing changed. The exemption is tied to license type and key type, not to having paid Google money at some point.

The Strategic Read for Builders

Two takeaways that outlive this specific migration.

First, vendor CLIs are a dependency, not a foundation. If a free, open tool sitting at the center of your workflow can be switched off on a published date, that tool is rented infrastructure. Treat it accordingly: keep your automation portable, and avoid hard-coding one vendor's command into the load-bearing parts of your pipeline.

Second, this is a reminder of why the open-weight, self-hosted end of the ecosystem keeps drawing this crowd. A model and a tool you actually control cannot be remotely retired on you. The trade is more setup and more maintenance in exchange for not waking up to a dead command. Today, plenty of Gemini CLI users are weighing exactly that trade.

Key Takeaways

• Today, June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extensions stop serving requests for Google AI Pro, Ultra, and free users.
• The replacement, Antigravity CLI, is built in Go, is agent-first with async background agents, and shares an engine with the Antigravity desktop app.
• The old CLI was open source (Apache 2.0); the new one is closed source, and Google admits there is no day-one feature parity.
• Exempt: Gemini Code Assist Standard/Enterprise licenses, Gemini Code Assist for GitHub via Google Cloud, and paid API keys.
• It installs via a single shell command (not npm), dropping a compiled binary reportedly named agy; Agent Skills, Hooks, Subagents, and Extensions (now plugins) carry over.
• Audit every script, CI step, and cron job that calls Gemini CLI today, because the backend going silent is what breaks your automation.

Sources: Google Developers Blog, google-gemini/gemini-cli Discussion #27274, The Register, Hacker News