Antigravity CLI vs Gemini CLI: What Changed and How to Migrate
By CodeAgentSwarm · Updated October 31, 2026
What happened: Gemini CLI was retired for personal accounts
Gemini CLI was Google's first terminal coding agent. It shipped as an open-source, Node-based tool you installed from npm and ran with the gemini command, signed in with a Google account, and pointed at a project. It got popular fast because it was free to start, had a large context window per session, and lived right in the terminal where developers already worked.
On June 18, 2026, Gemini CLI stopped serving free users, Google AI Pro and Ultra subscribers and Gemini Code Assist for individuals, and Google moved them to Antigravity CLI, the successor that runs under the agy command. Google announced it on its developers blog on May 19, 2026, and the project repository carries a pinned discussion explaining the change and the timeline.
- An important update: transitioning Gemini CLI to Antigravity CLI (the official announcement)
- The GitHub discussion on the gemini-cli repo, with the rationale and migration notes
Short version: Gemini CLI still exists, but only for enterprise Gemini Code Assist workflows on Google Cloud and paid Gemini API keys, as its README and the announcement explain. If you used Gemini CLI with a personal Google account, the next step is to install Antigravity CLI and let it import your old config, which is what the rest of this guide walks through.
The reason for the change is more than a rename. Antigravity CLI is a different architecture: a single compiled binary instead of a Node package, multiple models in the same terminal instead of Gemini only, and a multi-agent design instead of a single linear chat. The next section breaks those differences down.
Antigravity CLI vs Gemini CLI: what changed
Here is how Antigravity CLI compares to Gemini CLI across the things that actually affect your day. Each dimension lists the old behavior and the new one so you can see exactly what moved.
Runtime and install
- Gemini CLI: An npm package that needed Node installed. You updated it like any other Node tool, and your version depended on your local runtime.
- Antigravity CLI: One compiled binary, no Node or Python runtime required. You install it with a single script and run
agydirectly.
# Install Antigravity CLI (one binary, no Node needed)
curl -fsSL https://antigravity.google/cli/install.sh | bash
# Then run it
agyModels
- Gemini CLI: Gemini models only. The whole point was a Gemini-powered terminal agent, and you selected the Gemini model you wanted.
- Antigravity CLI: Gemini, Claude and open-weight models in the same terminal, depending on your plan. As of October 2026 the official model list offers Gemini 3.8 Flash on every plan, Gemini 4 Argon, Claude Sonnet 5.5 and Claude Opus 5.5 on paid Google AI plans, and Claude Sonnet 4.6, Claude Opus 4.6 and GPT-OSS 120B on the free tier until November 2, 2026. You choose with
/modelor--model.
This is the biggest practical change. Antigravity CLI is no longer a Gemini-only tool. It still leads with Gemini, but you can switch to a Claude or open-weight model when that fits the task better, without leaving agy.
Multi-agent vs single chat
- Gemini CLI: A single linear chat. One conversation, one agent, working through your request step by step.
- Antigravity CLI: Multi-agent by default. It can dispatch and coordinate sub-agents to work on parts of a task, rather than running everything as one thread.
Config and home directory
- Gemini CLI: Stored its settings, registered MCP servers, and preferences under the
~/.geminihome directory. - Antigravity CLI: Reuses the same
~/.geminihome, and on first launch it offers to convert your old Gemini CLI extensions and settings. Settings go to~/.gemini/antigravity-cli/settings.jsonand MCP servers to~/.gemini/config/mcp_config.json. That is what makes the migration painless.
Flags and everyday commands
- Turbo / skip permissions: run
agy --dangerously-skip-permissionsfor an unattended, auto-approving session. As with any yolo-style flag, use it carefully, since the agent will run actions you might have wanted to review. - Continue the last conversation:
agy -c. - Resume a specific conversation:
agy --conversation <id>.
If you want a fuller tour of the new tool on its own terms, the how to use Antigravity CLI guide covers the basics end to end.
How to migrate from Gemini CLI to Antigravity CLI
Migration is short on purpose. In practice it is two things: install Antigravity CLI, then accept the import prompt on first launch. Here are the steps.
1. Install Antigravity CLI
Run the install script. It drops a single binary, so you do not need to touch Node or your old npm install of Gemini CLI.
curl -fsSL https://antigravity.google/cli/install.sh | bash2. Launch agy and accept the import prompt
The first time you run agy, it detects your existing ~/.gemini home and shows a checklist of the Gemini CLI extensions and settings it can convert. Pick what you want. Settings land in ~/.gemini/antigravity-cli/settings.json, MCP servers in ~/.gemini/config/mcp_config.json, and the old and new tools coexist in the same home directory.
# First launch - it will ask to import your old Gemini CLI config
agyWhat the import brings across, according to the official migration guide:
- Your MCP servers, moved into
~/.gemini/config/mcp_config.json - Your extensions, converted into Antigravity plugins (custom commands become skills)
- Your session tokens, moved into the system keyring
- Not always: custom terminal themes, and workspace skills in
.gemini/skills/, which you move to.agents/skills/by hand
Because Antigravity CLI reuses ~/.gemini, you are not starting from a blank config. If you spent time wiring MCP servers or writing a global ~/.gemini/GEMINI.md under Gemini CLI, that work carries over instead of being thrown away.
3. Verify it works
Open a project, start a session, and confirm your MCP servers and instructions behave the way they did before. Try continuing your last conversation and resuming a specific one to make sure your history is reachable.
# Continue your last conversation
agy -c
# Resume a specific conversation by id
agy --conversation <id>Do not assume the import happened if you skipped the prompt. If your MCP servers or extensions are missing, you probably declined or missed the import on first launch. Check ~/.gemini/config/mcp_config.json for your servers, or run agy plugin import gemini to convert them now.
That is the whole migration. Since Gemini CLI no longer serves personal accounts, this is the move that keeps you current, and it costs a couple of minutes.
Running Antigravity CLI (and Claude and Codex) in one workspace
If you ran several Gemini CLI sessions at once, the thing you do not want to lose in the move is that multi-session workflow. Antigravity CLI sessions are still independent processes, so you can run many of them, and you can keep them in one place with CodeAgentSwarm.

CodeAgentSwarm is a desktop app for running several AI CLI sessions in parallel with real visibility. It runs on macOS, Windows and Linux, and it is not a model provider, so each Antigravity CLI session keeps using your own Google sign-in and your own agy install. The app just gives the sessions a place to live: multiple terminals in one workspace, the agent chosen per terminal from the SELECT AI AGENT picker.
This matters most during a transition. If your team had Gemini CLI sessions spread across tabs, you can move them to Antigravity CLI and keep the exact same multi-session setup, without juggling terminals by hand. And because the agent is per terminal, you are not locked in: one terminal on Antigravity CLI, another on Claude Code, a third on Codex CLI, all sharing one searchable history.
- Run several Antigravity CLI sessions at once, each independent
- Mix Antigravity CLI with Claude Code and Codex CLI per terminal
- Get a desktop notification when a session finishes or needs input
- Keep a searchable conversation history across every terminal
For the step-by-step on running many Antigravity sessions at once, see run multiple Antigravity CLI sessions. For the broader pattern across vendors, start with the AI CLI agent swarm hub.
If you are coming from the old Gemini CLI workflow, it carries over directly: running multiple Antigravity CLI sessions and the Antigravity agent swarm guide describe the same pattern on agy.
FAQ
Is Gemini CLI dead or deprecated?
For personal accounts, yes. On June 18, 2026 Gemini CLI stopped serving free users and Google AI Pro and Ultra subscribers, and Google moved them to Antigravity CLI, which runs under the agy command. Gemini CLI is still maintained for enterprise Gemini Code Assist customers on Google Cloud and works with paid Gemini API keys. The announcement is on the Google developers blog and there is a pinned discussion on the gemini-cli GitHub repo with the details.
Do I have to migrate from Gemini CLI to Antigravity CLI?
If you used Gemini CLI with a personal Google account, yes, because it no longer serves those accounts. Enterprise Code Assist customers and paid API key users can keep it. The upside is that migration is short: install Antigravity CLI with one script, then accept the import prompt on first launch. Your existing config comes across, so you are not rebuilding your setup from scratch.
Will my Gemini CLI config and MCP servers transfer?
Mostly. Antigravity CLI reuses the same ~/.gemini home directory and on first launch offers to convert your Gemini CLI extensions and settings. MCP servers move into ~/.gemini/config/mcp_config.json and your global ~/.gemini/GEMINI.md keeps working. Custom terminal themes may not carry over, and workspace skills in .gemini/skills/ need moving to .agents/skills/. If something is missing, run agy plugin import gemini.
What is the difference between Antigravity CLI and Gemini CLI?
Antigravity CLI ships as one compiled binary with no Node or Python runtime, while Gemini CLI was an npm/Node tool. Antigravity CLI offers Gemini, Claude and open-weight models in the same terminal, depending on your plan, whereas Gemini CLI was Gemini only. Antigravity CLI is multi-agent by default and can coordinate sub-agents, while Gemini CLI was a single linear chat. It also reuses the ~/.gemini home and imports your old config.
Is Antigravity CLI better than Gemini CLI?
It is the supported successor, so it is the one that will keep improving. It adds real capabilities over Gemini CLI: a single-binary install with no Node runtime, several model families in one terminal, and a multi-agent design. Whether every change suits your workflow is up to you, but for personal accounts Gemini CLI no longer works, so Antigravity CLI is the current tool to use.
Can I still use Gemini CLI?
Only in some setups. Gemini CLI is still maintained for enterprise Gemini Code Assist customers on Google Cloud and accepts paid Gemini API keys. With a free account or a Google AI Pro or Ultra subscription it stopped serving requests on June 18, 2026, so the path for those users is to install Antigravity CLI and import their config.
Does Antigravity CLI use Gemini models?
Yes, and it leads with them. As of October 2026 Gemini 3.8 Flash is available on every plan and Gemini 4 Argon on paid Google AI plans. It also goes beyond Gemini: the same terminal offers Claude models and, on the free tier until November 2, 2026, GPT-OSS 120B. Choose with /model or --model, and run agy models to see what your plan includes.