Google is retiring Gemini CLI. On June 18, 2026, the Gemini CLI and Gemini Code Assist IDE extensions stop serving requests for individual users, including everyone on Google AI Pro and Ultra and the free Gemini Code Assist tier. The replacement is Antigravity CLI, announced at I/O and available now.

If you standardized a workflow on Gemini CLI, this is the bill arriving for a tool you thought was free.

What’s Actually Changing

  • Individual tiers sunset June 18. Free, Pro, and Ultra users on Gemini CLI must migrate or lose access. The legacy tool simply stops responding.
  • Enterprise is untouched. Gemini Code Assist Standard and Enterprise licenses, and the GitHub integration via Google Cloud, keep working. The people paying the most feel nothing.
  • Antigravity CLI is the path. A Go rewrite, faster, with async processing so long tasks don’t lock your session. It carries over the important primitives: Agent Skills, Hooks, Subagents, and Extensions (rebranded as Antigravity plugins).

It is, on the technical merits, a better tool. That is not the part worth paying attention to.

The Asymmetry Is the Story

A free vendor CLI is not a gift. It is customer acquisition with the cost deferred. You adopt it because it is good and free, you wire it into your shell, your scripts, your CI, your muscle memory. The price you didn’t pay up front gets collected later, as a forced migration on a date the vendor picks.

Google gave about a month of notice and a migration checklist. That is responsible as these things go. It does not change the shape of the deal: the people who invested the most in the free tier are the ones now doing unpaid migration work, while the enterprise accounts that pay carry on undisturbed. Adoption flowed one way; the cost of the transition flows the other.

Antigravity CLI does not have 1:1 feature parity with Gemini CLI out of the gate.

— Google, on the Antigravity CLI transition

That sentence is the whole risk in miniature. “Migrate to the better tool” and “some of your workflow no longer exists” are being announced in the same breath.

And It’s Google, Specifically

This lands harder coming from Google than it would from almost anyone else, because Google has a reputation it has earned product by product. There is a website, Killed by Google, whose only job is to count what the company has shut down. It sits at 305 dead products (66 apps, 215 services, 24 pieces of hardware), and that’s before Gemini CLI joins the list. The average Google product lives about 5.2 years before it’s switched off. Reader, Inbox, Stadia, Domains, Hangouts: an entire generation of tools people built habits, workflows, and businesses on, retired out from under them.

Gemini CLI launched around mid-2025. It’s being retired roughly a year later, fast even by the graveyard’s own grim average. So this isn’t a freak event nobody could have priced in. It’s the most predictable company in tech doing the single most predictable thing it does. Standardizing a critical workflow on a free, year-old Google tool was a bet against a track record that fills a memorial site, and the house won again.

I Have Skin in This

I wrote a post on a Gemini and Claude Code hybrid workflow: use one for breadth, the other for depth, glued together at the CLI. June 18 takes a chainsaw to half of it. The commands change, the config moves, the flags I documented may or may not survive the port. Anyone who followed that post is now doing the same migration I am.

This is the same lesson as the walled-garden crackdown, pointed the other direction. There the worry was a vendor closing access. Here it is a vendor changing the locks on a tool you depend on. The mechanism differs; the exposure is identical. You do not own the harness.

Standardize on the swappable layer

The hedge isn’t picking a different vendor to be loyal to. It’s keeping the thing you depend on replaceable. The reason I like wrappers and model-agnostic launchers is precisely this: when the framework stays put and only the backend swaps, a vendor’s deprecation is a config change, not a workflow rebuild. Depend on interfaces you control, not CLIs someone else versions.

What This Isn’t

The cynical read is too easy, so the caveats matter:

  • Antigravity is a real upgrade. Go, async, no session locks. For heavy users it may be strictly better once parity lands.
  • The core was open source. Gemini CLI shipped under a permissive license, so the community can keep a fork breathing if it wants. This is not a total lock-out.
  • A month of notice is not a rug-pull. Compare it to vendors who deprecate with a changelog line and no migration path. Google did the work to make this survivable.

The complaint isn’t that Google behaved badly. It’s that “free, beloved, and yours” was never the actual offer, and June 18 is when that becomes legible.

The Takeaway

Every free CLI from a vendor with a roadmap is a rental with the rent hidden in switching costs. Use them, they’re great. Just don’t confuse a tool you can use for free with a tool you own. Keep your real dependency on the layer you control, so the next deprecation notice is an afternoon, not a month.

Gemini CLI had a good run. The expiry date was always there. June 18 is just when it printed.

Related Posts