Gemini CLI Is Dead: Migrate to Antigravity CLI Before Today’s Deadline

Google killed Gemini CLI for free users and Google AI Pro/Ultra subscribers on June 18, 2026, replacing it with the closed-source Antigravity CLI. The migration requires renaming the `url` field to `serverUrl` in MCP config files, a silent failure that breaks MCP servers if missed. Enterprise Gemini Code Assist users and paid API key holders are unaffected.

If you have automation scripts or CI pipelines calling gemini , they stopped working today. Google killed Gemini CLI for free users and Google AI Pro/Ultra subscribers on June 18, 2026 — the replacement is Antigravity CLI agy , part of the broader Antigravity 2.0 platform https://developers.googleblog.com/an-important-update-transitioning-gemini-cli-to-antigravity-cli/ . The migration is not optional, and there are a few silent failures that will bite you if you just swap the binary without reading the changelog. The 4-Step Migration If you need this working right now, here are the four steps: 1. Install Antigravity CLI curl -fsSL https://antigravity.google/cli/install.sh | bash agy --version Windows users: irm https://antigravity.google/cli/install.ps1 | iex in PowerShell. The new binary is named agy , not antigravity . 2. Authenticate agy This opens a browser for OAuth. If you are on SSH, you will get a URL to complete on a local machine — finally a sensible flow for headless environments. 3. Import your plugins python agy plugin import gemini This converts Gemini CLI extensions to Antigravity plugins and migrates MCP server config where possible. It is not perfect — see the gotcha below. 4. Move your skills directory and update config files mkdir -p .agents mv .gemini/skills .agents/skills Your context files GEMINI.md , AGENTS.md carry over unchanged. The MCP config file is where things get tricky. The Silent Failure: One Field Rename That Breaks Your MCP Servers This is the change that will quietly break your setup without any error message. In your MCP configuration, the url field is now serverUrl : // OLD — .gemini/settings.json MCP inline config { "url": "https://your-mcp-server.example.com" } // NEW — .agents/mcp config.json { "serverUrl": "https://your-mcp-server.example.com" } If you miss this rename, Antigravity CLI starts fine but never calls your MCP servers. The migration guide at Agentpedia https://agentpedia.codes/blog/gemini-cli-to-antigravity-cli-migration flags this as the most common source of post-migration confusion. Here is the full path and field mapping: | What | Old Path/Value | New Path/Value | |---|---|---| | Binary | gemini | agy | | Workspace skills | .gemini/skills/ | .agents/skills/ | | Global skills | ~/.gemini/skills/ | ~/.gemini/antigravity-cli/skills/ | | Global MCP config | ~/.gemini/settings.json | ~/.gemini/antigravity-cli/mcp config.json | | Workspace MCP config | .gemini/settings.json | .agents/mcp config.json | | MCP server URL field | url | serverUrl | Who This Does Not Affect Worth clarifying before the panic sets in: this forced migration hits free users, Google AI Pro/Ultra subscribers, and free Gemini Code Assist users only. If your organization has a Gemini Code Assist Standard or Enterprise license — or if you are using the Gemini API with a paid API key — Gemini CLI keeps working unchanged. Google confirmed the enterprise version will continue to receive the latest model releases, bug fixes, and security updates. The Part Google Did Not Announce Loudly Gemini CLI launched under Apache 2.0 with full source code on GitHub. It accumulated 100,000+ stars and 6,000 merged community PRs in under a year. Antigravity CLI is closed-source — the GitHub repository contains only a changelog, a README, and a GIF. Reaction on the official GitHub discussion https://github.com/google-gemini/gemini-cli/discussions/27274 was blunt: 265 downvotes, 6 upvotes, with contributors pointing out they had worked for free on code that now exclusively serves enterprise customers. This is a recognizable playbook — build community goodwill with open-source, monetize through closed-source successors. A 100,000-star project retired in under a year is worth noting if you are deciding how much infrastructure to build on any Google developer product. What Is Actually Better in Antigravity CLI Credit where it is due: Antigravity CLI is a better tool in some genuine ways. Built in Go instead of Node.js, it starts faster, uses less memory, and works cleanly in headless and SSH environments without fighting Node dependency chains. Background async workflows let you kick off a large refactor and keep using your terminal — the primary agent can spin up parallel subagents with isolated context windows, which is a real improvement for multi-step pipelines. Gemini 3.5 Flash runs up to 12x faster inside Antigravity compared to Gemini CLI, according to benchmarks from Augment Code https://www.augmentcode.com/tools/google-antigravity-vs-gemini-cli . If you run heavy agentic coding workflows, you will likely notice the difference after migration. The community complaints about missing features — clipboard pasting, some MCP integrations — are real, and Google acknowledged there is no 1:1 feature parity right out of the gate. Check the official Antigravity migration docs https://antigravity.google/docs/gcli-migration for the current known-gaps list before moving production workflows. After the Migration: Quick Validation Before you close the terminal, run through this checklist: - Reproduce a task you previously ran in Gemini CLI - Verify your agent reaches expected MCP tools - Confirm workspace skills execute correctly - Check MCP server calls fire — watch for the serverUrl issue specifically - Validate hooks fire at expected lifecycle moments The migration takes about 10 minutes if nothing unusual is broken. The MCP field rename is the one to double-check. Enterprise users on Standard or Enterprise plans: you have nothing urgent to do today.