Google Is Killing the Gemini CLI for 'Antigravity.' I Just Wrote a Guide to It.
Four days after I walked through installing the Gemini CLI, Google is retiring it for a new Antigravity CLI. The migration is annoying. The part that should bother you is what changed underneath.
By Dev Banerjee · · 3 min read
query://toolsLast week I wrote a guide to living in the terminal with the Gemini CLI. This week Google announced it is retiring it. The timing is funny in the way that only happens to people who write tutorials, so let me eat the irony and tell you what actually changed, because it matters more than my embarrassment.
As of June 18, the Gemini CLI and Gemini Code Assist extensions stop serving consumer requests. Personal accounts on Google AI Pro, Ultra, and the free tier can no longer invoke the old tool. Google is pointing everyone at a new Antigravity CLI instead. Enterprise accounts keep the old version for now.
What Antigravity is
The replacement is not a renamed Gemini CLI. Antigravity is built in Go, designed around multi-agent and asynchronous background workflows rather than the single-agent loop the Gemini CLI used. On paper it is more capable: you can hand it longer-running jobs and let agents work in the background. That is a real step up in ambition, and for heavy automation it will probably be the better tool.
If you followed my guide, the muscle memory transfers more than you would expect. You still work from the terminal, still reference files, still pipe things in. The commands change, the auth flow is similar, and the migration itself is a couple of hours of updating scripts and CI pipelines, not a rewrite.
The part that should actually bother you
What turns this from a changelog into a story is the part I did not see coming. The Gemini CLI was open source. Antigravity CLI is not.
That switch drew immediate pushback, and the pushback is correct. The Register called it a bait-and-switch, and developers who built on the open tool are right to feel it. When you adopt an open-source CLI, part of what you are buying is insurance: if the vendor abandons it, the community can fork it, and you are never fully trapped. You wire it into your workflow precisely because the floor cannot fall out.
Replacing that with a proprietary tool removes the insurance. The new thing might be better today, but you are now depending on Google's roadmap with no fork to fall back on, from a company whose own messaging app graveyard is a meme. I built my last guide partly on the logic that an open CLI was a safe foundation. That logic was wrong, and I would rather say so than pretend the update is purely an upgrade.
What to actually do
If you set up the Gemini CLI recently, you have until your usage breaks to migrate, which for personal accounts is now. The practical path: install the Antigravity CLI, port your most-used commands and any CI steps, and confirm your auth still works. The everyday workflow survives the move.
But take the lesson with you when you pick the next tool. Open source mattered here not for ideology but for leverage, and the developers who chose the Gemini CLI partly because it was open just learned what that insurance was worth when it lapsed. I am updating my own guide with a note pointing here. Next time I recommend a free vendor CLI, I will say the quiet part out loud: free and open are not the same promise, and only one of them protects you when the vendor changes its mind.
enjoyed this one?_
Get the next one in your inbox.
One email every morning. The AI news that matters, decoded in five minutes.
up_next → Tools
DeepSeek Made Its 75% Price Cut Permanent. The Floor Just Fell Out of the Token Market.
DeepSeek V4 Pro now starts at $0.003625 per million tokens, runs a 1M context on Huawei silicon, and just turned a promotion into the new normal. What the price war means for everyone's API bill.
