Gemini CLI → Antigravity CLI Migration

Google announced on May 19, 2026 that Gemini CLI is being transitioned into Antigravity CLI. For paying enterprise customers, nothing changes. For everyone on a Google AI Pro, Ultra, or free Gemini Code Assist for individuals account, Gemini CLI stops serving requests on June 18, 2026. This is the migration plan you can run in an evening, with rollback if a critical workflow breaks.

1. The Announcement

Two Google channels published the transition on the same day. The Google Developers Blog laid out the timeline. The @geminicli account on X committed to a 30-day migration window for individual-tier users and an explicit no-action-required carveout for enterprise customers.

Google DeepMind framed the bigger picture from a separate official account — the CLI is one piece of a three-surface developer offering, not a standalone product:

The official migration docs at antigravity.google/docs/gcli-migration are the source of truth for the file-by-file mapping. The steps below follow them in order, with the gotchas called out where the docs leave them implicit.

2. TL;DR

• Deadline: June 18, 2026 (individual tier)
• Affected: Google AI Pro, Google AI Ultra, free Gemini Code Assist
• Not affected: Code Assist Standard / Enterprise, paid Gemini API keys
• Replacement: Antigravity CLI (binary: agy)
• One-command migration: agy plugin import gemini
• Manual moves needed: .gemini/skills/ → .agents/skills/, MCP config to mcp_config.json
• Field rename: remote MCP url → serverUrl
• Context files: GEMINI.md and AGENTS.md keep working unchanged
• Parallel install: safe — gemini and agy coexist
• Reading time of this guide: 14 minutes; doing the work: about 45 minutes

3. The Timeline

4. Who Is Affected

Run this quick check before reading further:

• You log into Gemini CLI with a personal Google account. You are affected — this is the free / consumer flow.
• You pay for Google AI Pro or Google AI Ultra. You are affected. Antigravity CLI uses the same subscription.
• You use Gemini Code Assist for individuals (free tier). You are affected. Both Gemini CLI and the Code Assist IDE extension stop on June 18.
• You authenticate Gemini CLI with a paid Gemini API key. You are not affected. Gemini CLI continues for paid API key users.
• Your org has a Gemini Code Assist Standard or Enterprise license. You are not affected. Enterprise CLI access remains unchanged.

5. Enterprise Carveout

Per the Google Developers Blog: “If your organization uses Gemini CLI or our IDE extensions via a Gemini Code Assist Standard or Enterprise license, or if your organization uses Gemini Code Assist for GitHub through Google Cloud, your access remains unchanged. We'll continue to support Gemini CLI and Gemini Code Assist with access to the latest Gemini models and other updates.”

Concretely, enterprises retain three options:

• Keep Gemini CLI on Standard / Enterprise license — no migration needed.
• Keep Gemini CLI on a paid API key — no migration needed.
• Adopt Antigravity CLI alongside, using GCP project credentials. See the official enterprise page for the GCP project linkage details.

If you are an enterprise admin reading this for someone else, the headline for you is plan a pilot, do not panic-migrate the org. The deadline only binds the consumer tier.

6. Pre-Flight Checklist

Before you start the migration, confirm:

• Your machine can install a Go-distributed binary (agy) — you have curl, irm, or admin shell access.
• You know which Google account is on your Gemini CLI today (the migration carries the same account forward).
• You can list your installed Gemini CLI extensions (gemini extension list).
• Your ~/.gemini/ directory is intact (it holds your global rules and skills).
• Workspace projects with custom .gemini/ folders are identified — each one needs a manual move for workspace-scope skills.
• If you script Gemini CLI calls from CI or cron, you have a flag-day plan to switch the binary name (gemini → agy) and the auth flow.

7. Step 1: Install Antigravity CLI

One install command per platform, from the official README:

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

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

# Windows CMD
curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd

After installation, verify:

agy --version
# expected: a version string is printed

The binary is named agy, not antigravity. If you script CLI calls, this is your rename. Gemini CLI's geminibinary stays in place; the two coexist.

8. Step 2: Authenticate

First run opens an auth flow. Two variants:

• Local terminal. Run agy. Your default browser opens. Sign in with the same Google account you used for Gemini CLI. The token is stored in your system keyring.
• Remote / SSH. Run agy. The CLI detects the SSH session and prints an authorization URL. Open it on your local machine, complete the OAuth flow, and the SSH session picks up the token. This was a notable pain point in early Gemini CLI — now first-class.
• Enterprise. During onboarding you can connect a GCP project. Calls then bill against that project. The official enterprise docs cover the specifics.

9. Step 3: Import Plugins

On first launch, Antigravity CLI prompts to migrate Gemini CLI extensions to Antigravity plugins. If you skip the prompt or are installing on a fresh machine, run the import explicitly:

agy plugin import gemini

Sample output from the official migration docs, walking a multi-component extension:

[ok]    conductor
          - skills      : skipped (not found)
          - agents      : skipped (not found)
          ✔ commands    : 6 processed (converted to skills)
          - mcpServers  : skipped (not found)
          - hooks       : skipped (not found)
[ok]    google-workspace
          ✔ skills      : 6 processed
          - agents      : skipped (not found)
          ✔ commands    : 4 processed (converted to skills)
          ✔ mcpServers  : 1 processed
          - hooks       : skipped (not found)

10. Step 4: Move MCP Configs

Gemini CLI stored MCP servers inline in settings.json. Antigravity CLI uses a separate file. Move them:

And one field rename in the JSON itself:

// Gemini CLI (settings.json)
{
  "mcpServers": {
    "my-remote-mcp": {
      "url": "https://example.com/mcp"   // or the deprecated "httpUrl"
    }
  }
}

// Antigravity CLI (mcp_config.json)
{
  "my-remote-mcp": {
    "serverUrl": "https://example.com/mcp"
  }
}

Remote MCP servers will fail silently if you copy url across without renaming. Local MCP server entries with command + args do not need the rename. For background on MCP configuration, see our MCP tutorial.

11. Step 5: Move Workspace Skills

Global skills under ~/.gemini/skills/ load automatically — no action needed. Workspace skills under .gemini/skills/ must move to .agents/skills/:

# Per project, from the workspace root:
mkdir -p .agents
git mv .gemini/skills .agents/skills
# Or, if not in git:
mv .gemini/skills .agents/skills

If a workspace already had a .agents/skills/ folder (the dual-location case the Gemini CLI docs allowed for), keep that one and remove the .gemini/skills/ copy. For authoring patterns, see our Antigravity skills setup guide.

12. Step 6: Verify Hooks and Context

Two things to confirm before you call the migration done:

• Context files load. GEMINI.md and AGENTS.md in the workspace, plus ~/.gemini/GEMINI.md globally, all keep working unchanged. Open a session and ask the agent to recite a known rule from your file.
• JSON hooks fire. If you authored JSON hooks against Antigravity 2.0 or Gemini CLI, they apply in Antigravity CLI on the same lifecycle moments. Touch a file or run a sample tool call to confirm a hook you know about actually fires.

For rules patterns, see our rules examples and GEMINI.md system prompt guide.

13. Step 7: Real-Task Validation

The one step you do not skip. Pick a task you did yesterday in Gemini CLI — a refactor, a research session, a multi-file edit — and run it in Antigravity CLI on the same repo. Compare:

• Did the agent reach the same tools at the same steps?
• Did your skills slash-command in the right places?
• Did MCP-server calls fire? (Watch for silent serverUrl failures here.)
• Did the context files (GEMINI.md, AGENTS.md) shape behavior the same way?
• Were hooks invoked at the lifecycle moments you expect?

Twenty to thirty minutes on a representative task gives you 90% of the signal you need. If everything reproduces, you are done. If one thing breaks, file it and fall back to Gemini CLI for that workflow until you have a fix.

14. Rollback Plan

Antigravity CLI and Gemini CLI coexist on the same machine. They are separate binaries (agy vs gemini), separate config trees (~/.gemini/antigravity-cli/ alongside ~/.gemini/), and separate auth flows. Until June 18, 2026, your rollback for any individual workflow is simply: keep running gemini for that one task.

After June 18 the rollback options narrow to:

• Upgrade to an enterprise license (Gemini Code Assist Standard / Enterprise).
• Switch to a paid Gemini API key.
• Use Antigravity 2.0 (the GUI) instead of the CLI for the affected workflow.
• Use a different agent CLI entirely. See our alternatives roundup for the current landscape.

15. What Changes At a Glance

16. FAQ

17. Verdict

If you do exactly one thing today: install Antigravity CLI on the machine where you used Gemini CLI most. Everything else is a smaller commitment from there.

Sources

• Google Developers Blog — An important update: Transitioning Gemini CLI to Antigravity CLI
• @geminicli on X — transition announcement
• Antigravity CLI — Migrating from Gemini CLI (official docs)
• Introducing Google Antigravity CLI — antigravity.google
• Introducing Google Antigravity 2.0 — antigravity.google
• Antigravity CLI Overview — official docs
• google-antigravity/antigravity-cli — GitHub repository