Google Kills Gemini CLI Tomorrow. The Replacement Is Closed-Source. If You Wired a Free Vendor CLI Into Your Pipeline, Today Is the Lesson.
If anything in your automation shells out to gemini, it breaks tomorrow. Google is retiring Gemini CLI for consumer accounts on June 18, 2026, that's one day from when this posts. The standalone CLI and the Gemini Code Assist IDE extensions stop serving requests for individual users, and the path forward is Antigravity, a closed-source, Go-based tool that ships as a binary called agy. If you've been treating the deprecation notice from May as a someday problem, someday is tomorrow.
I want to be precise about who this hits, because the panic version of this story is wrong. If you're on a Gemini Code Assist Standard or Enterprise license, or you use Code Assist for GitHub through Google Cloud, your access is unchanged. The cutoff is for the consumer tiers: Google AI Pro, Ultra, and the free Gemini Code Assist for individuals. That's still a lot of solo developers: the people most likely to have quietly wired a free CLI into a cron job and forgotten about it.
What's actually changing
Google announced this at I/O on May 19, 2026, and the framing was consolidation: one brand, Antigravity, instead of a scatter of separately-named developer tools. The Antigravity ecosystem is a desktop app (Antigravity 2.0) plus a terminal interface (Antigravity CLI), both running on a shared agent harness built for multi-agent orchestration. That's a real product and it may well be good. But notice what moved. Gemini CLI was the kind of thing you could read, script around, and reason about. The replacement is a closed-source binary aimed at "complex, multi-agent orchestration," which is a different product for a different user than the person who just wanted a model in their terminal.
This is not a version bump. It's a different tool with a different name, a different language, and a different license, arriving on a date Google picked. "Migrate to Antigravity" is the headline, but for a lot of small setups the honest description is "rewrite the part of your workflow that called Gemini CLI, against a deadline."
Why this keeps happening to free vendor tools
Here's the part worth internalizing past this specific CLI. A free command-line tool from a megacap is not infrastructure. It's a marketing funnel. It exists to get you into the ecosystem: to make the model feel close, the friction low, the lock-in comfortable. And funnels get restructured when the company decides the funnel should point somewhere else. Gemini CLI did its job: it seeded a generation of developers on Google's models. Now Google wants those developers on Antigravity, so the old door closes.
None of that is a betrayal. It's just what free vendor tools are for. The mistake isn't trusting Google. The mistake is confusing "this is free and convenient" with "this is stable enough to build on." Interactive use (you, at a keyboard, typing prompts) is exactly what these tools are good for, and if Gemini CLI dies you shrug and open something else. The danger zone is when the free tool becomes load-bearing: a deploy script, a content pipeline, a nightly job that some other thing depends on. That's where a deprecation date turns into a broken Tuesday.
What I'd actually do before tomorrow
First, grep your own machine. Search your scripts, cron entries, Makefiles, CI config, and any automation for gemini and the Code Assist extension. You're looking for the places where a human isn't in the loop: those are what break silently. Interactive use can wait; pipeline calls can't.
Second, decide per-call whether you even need a Google model there. A lot of "I used Gemini CLI" turns out to be "I needed any decent model in a shell," and the fix is a different CLI you control, not a like-for-like migration to Antigravity. If the answer is genuinely "I need Gemini specifically," then move to the supported path now, while it's a calm afternoon instead of a fire.
Third, and this is the durable lesson: for anything that runs unattended, put a layer you own between your automation and the vendor. A thin script, your own API call, a small wrapper: something where swapping providers is a config change, not a rewrite. The whole reason this deprecation can ruin your week is that the vendor's tool was sitting directly in your critical path. Don't rebuild that mistake on top of Antigravity.
The honest counter-take
It's fair to say I'm making a bigger deal of this than most people's setups warrant. The genuine truth is that the majority of Gemini CLI usage was interactive (developers poking at it, not production pipelines) and for those people June 18 is a non-event. They'll install something else and never think about it again. If that's you, this whole post is a shrug, and that's fine.
But "I only use it interactively" is exactly what people say right up until they remember the one script. The cost of checking is ten minutes with grep. The cost of being wrong is a dead automation discovered at the worst possible time, on a date you didn't choose. Google picked tomorrow. Spend the ten minutes today.
Author
Lukas
@lukcombinator