Gemini CLI to Antigravity CLI Migration Guide: The June 18 Deadline

Official Sources

Last updated: June 17, 2026

Tomorrow, June 18, 2026, Gemini CLI stops serving requests for free-tier and Google AI Pro/Ultra users. If you rely on the gemini binary in your terminal, CI pipelines, or automation scripts, you have roughly 24 hours to migrate to Antigravity CLI or your workflows will break.

This guide covers exactly what to do: installation, config migration, the silent MCP bug that breaks tool calls, and the CI/CD changes you cannot skip.

Who Is Affected

Must migrate by June 18:

• Free-tier Gemini CLI users
• Google AI Pro and Ultra subscribers
• Anyone using Gemini Code Assist IDE extensions outside enterprise agreements
• New Gemini Code Assist for GitHub installations (blocked after June 18)

Exempt from migration:

• Gemini Code Assist Standard or Enterprise license holders
• Organizations using GitHub integration through Google Cloud
• Anyone accessing Gemini via paid API keys (not CLI)

If you are on an enterprise license, your Gemini CLI access continues. But the community is moving to Antigravity, so the ecosystem support for Gemini CLI will decline.

What Changes

Antigravity CLI is a ground-up Go rewrite, not a fork of the original TypeScript stack. The core features transfer: Agent Skills, Hooks, Subagents, and Extensions (now called plugins). But the implementation details differ in ways that will break existing automation.

Key differences:

Google explicitly states there will not be 1:1 feature parity at launch. The migration script does not touch your CI configs, cron jobs, or shell aliases. You must audit those manually.

Step 1: Install Antigravity CLI

macOS/Linux:

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

Or via Homebrew:

brew install --cask antigravity-cli

Windows (PowerShell):

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

Verify installation:

agy doctor

This runs end-to-end validation. Fix any issues before proceeding.

Step 2: Authenticate

Run agy and complete the OAuth flow. The settings file lands at ~/.gemini/antigravity-cli/settings.json.

If you were using a custom API key with Gemini CLI, you will need to reconfigure it in the new settings file.

Step 3: Import Your Extensions

Antigravity CLI includes a migration command for Gemini extensions:

agy plugin import gemini

This converts your Gemini extensions to Antigravity plugins. Review the output for any warnings about incompatible extensions.

Step 4: Move Your Skills

Workspace skills move from .gemini/skills/ to .agents/skills/:

git mv .gemini/skills .agents/skills

Global skills move from ~/.gemini/skills/ to ~/.gemini/antigravity-cli/skills/:

mv ~/.gemini/skills ~/.gemini/antigravity-cli/skills

Step 5: Fix the MCP Config (Critical)

This is where most migrations silently fail. Antigravity CLI moves MCP server configuration from inline entries in settings.json to a dedicated mcp_config.json file.

The trap: Remote MCP servers use a different field name. You must rename url to serverUrl. If you keep url, the server appears to load at startup and passes initial checks. It only fails hours later when you actually invoke a tool - no error at startup, just silent failure during the session.

Before (Gemini CLI settings.json):

{
  "mcpServers": {
    "myserver": {
      "url": "https://mcp.example.com/v1"
    }
  }
}

After (Antigravity CLI mcp_config.json):

{
  "mcpServers": {
    "myserver": {
      "serverUrl": "https://mcp.example.com/v1"
    }
  }
}

Run agy inspect after configuration to confirm your plugins, skills, and MCP servers loaded correctly.

Step 6: Update CI/CD and Automation

The migration script does not touch scripts, cron jobs, or CI configs that invoke the gemini binary directly. You must find and replace these yourself.

Audit your codebase:

grep -r "gemini" .github/workflows/
grep -r "gemini" scripts/
grep -r "^gemini " ~/.bashrc ~/.zshrc ~/.bash_profile

Replace all gemini calls with agy. Common locations:

• GitHub Actions workflows
• GitLab CI/CD pipelines
• Jenkins scripts
• Cron jobs
• Shell aliases in dotfiles
• Docker entrypoints
• Makefile targets

Known Issues at Launch

Missing ACP mode: If you use orchestration bridges with stdio mode, there is no drop-in replacement. GitHub Issue #31 tracks this gap. Workaround: use the HTTP transport or wait for the feature.

Quota change: The daily 1,000-request limit becomes a weekly compute-based cap. Community reports describe exhaustion after roughly 2,000 lines of generated code, with multi-day cooldowns. Plan heavy generation work accordingly.

No backward compatibility: Even features marked as "carried forward" may have different flag names and environment variable conventions. Test everything before June 18.

Migration Checklist

Before June 18, confirm:

• agy doctor passes
• agy inspect shows all plugins, skills, and MCP servers
• Remote MCP entries use serverUrl not url
• All gemini binary references in CI/CD replaced with agy
• Shell aliases updated
• Heavy generation work completed or quota management understood

The migration takes roughly 45 minutes for interactive setup. Auditing automation infrastructure takes longer. Start now.

If You Miss the Deadline

After June 18:

• Free-tier users: no access via CLI
• Pro/Ultra users: no access via CLI
• Enterprise users: unchanged access

You can still use Gemini models via the API with paid keys, but the CLI convenience disappears. If you need CLI access without enterprise licensing, Antigravity CLI is now the only path.

FAQ

Does Antigravity CLI work with Claude or GPT models?

Yes. Unlike Gemini CLI which was Gemini-only, Antigravity CLI supports multiple providers including Gemini, Claude, and GPT-OSS models through the /model command.

Can I keep using Gemini CLI after June 18 if I have an API key?

No. The CLI itself stops serving requests. Having an API key lets you call Gemini models programmatically, but the gemini binary will not work. You would need to build your own tooling or use Antigravity CLI.

What happens to my existing Gemini CLI skills?

They need to move to the new directory structure. Use git mv .gemini/skills .agents/skills for workspace skills. The skill format itself remains compatible.

Is there a way to test the migration before June 18?

Yes. Install Antigravity CLI now and run agy doctor and agy inspect. Both tools can coexist temporarily. Validate your config migration before removing Gemini CLI.

Why did Google give only 30 days notice?

Google announced on May 19, 2026 with a June 18 deadline - roughly one sprint cycle. The reasoning was not explained in the blog post. Enterprise customers are exempt, which suggests this is a cost-reduction move for free-tier support.

Will Gemini CLI get updates after June 18 for enterprise users?

Yes, enterprise users retain access with "the latest Gemini models and other updates" according to the announcement. But community investment will shift to Antigravity CLI.

How do I report bugs in Antigravity CLI?

Use the GitHub repository at github.com/google/antigravity-cli. The ACP mode gap is tracked as Issue #31.

What is the weekly quota limit exactly?

Google has not published specific numbers. Community reports suggest roughly 2,000 lines of generated code before throttling kicks in, with multi-day cooldown periods. Monitor your usage and plan heavy generation work accordingly.