Antigravity CLI Migration from Gemini CLI: Complete Guide Before June 18

Why Migrate from Gemini CLI?

Google announced on May 19, 2026: Gemini CLI will stop serving requests for individual users on June 18, 2026. Free accounts, Google AI Pro, and Ultra subscriptions are all affected.

The replacement is Antigravity CLI (binary: agy). It’s not just a rename — it’s built in Go, noticeably faster than the old Node.js-based Gemini CLI, and shares the same agent harness as Antigravity 2.0 desktop.

The good news: your core workflows survive. Agent Skills, Hooks, Subagents, and Extensions (now called Plugins) all carry over.

Who Needs to Migrate?

User Type	Must Migrate?
Free Gemini Code Assist for individuals	✅
Google AI Pro / Ultra subscription	✅
Gemini Code Assist Standard / Enterprise	❌
Google Cloud API key users	❌

Quick check: if which gemini finds a binary and you’re not on an enterprise license, you need to migrate.

How to Install Antigravity CLI?

macOS and Linux:

curl -fsSL https://antigravity.google/cli/install.sh | bash

The binary installs to ~/.local/bin/agy. If your shell can’t find it:

export PATH="$HOME/.local/bin:$PATH"
# Make it permanent
echo 'export PATH="$HOME/.local/bin:$PATH"' >> ~/.bashrc

Verify:

agy --version

Windows (PowerShell):

irm https://antigravity.google/cli/install.ps1 | iex

How to Import Gemini CLI Config?

One command handles most of the migration:

agy plugin import gemini

This imports skills, hooks, and extensions automatically. But some things need manual fixes:

What You Need to Change Manually

Gemini CLI	Antigravity CLI	Notes
.gemini/skills/	.agents/skills/	Directory renamed
MCP config url field	serverUrl	Remote MCP servers only
GEMINI.md	Unchanged	Both files are recognized
AGENTS.md	Unchanged	Both files are recognized

MCP Config Migration Example

Old Gemini CLI format:

{
  "mcpServers": {
    "my-server": {
      "url": "https://my-mcp-server.example.com/sse"
    }
  }
}

New Antigravity CLI format (rename url to serverUrl):

{
  "mcpServers": {
    "my-server": {
      "serverUrl": "https://my-mcp-server.example.com/sse"
    }
  }
}

Local MCP servers (using command field) don’t need changes.

How to Verify the Migration?

cd your-project
agy

# Inside the TUI, check loaded tools
/tools

If your Skills and MCP tools all show up, you’re done.

Known Issues After Migration

Token consumption spike. Antigravity CLI defaults to Gemini 3.5 Flash, which consumes significantly more tokens than old Gemini 3. Community reports suggest 3-5x increase for similar tasks. Monitor your usage if you’re on pay-per-token.

WSL authentication doesn’t persist. You need gnome-keyring installed in WSL for agy to remember your login between sessions.

Antigravity 1.0 users got wiped. The May 19 auto-update cleared configurations for existing Antigravity 1.0 users. If you were on 1.0, rebuild your AGENTS.md from scratch.

Migration Timeline

Date	Event
May 19	Antigravity CLI launches. 30-day migration window begins.
May 20 – Jun 17	Parallel period. Both CLIs work.
June 18	Gemini CLI stops serving individual-tier requests.

Don’t wait until the last day. Install agy now, run a few real tasks, and confirm everything works.

Related Links

• Official Google Migration Announcement
• Antigravity CLI Installation Docs
• Antigravity CLI Getting Started