Practical guides

Moving from Gemini CLI to Antigravity CLI: installation and migration

Since June 18, 2026, Gemini CLI no longer serves free, Google AI Pro and AI Ultra accounts. Who is affected, how to install Antigravity CLI and migrate skills, extensions and MCP servers.

By ·

On May 19, 2026, Google announced that Antigravity CLI would replace Gemini CLI for individual accounts (Google Developers Blog). The switch happened on June 18, 2026. This guide sums up who is affected, then covers installation and migration according to Antigravity's official documentation, verified on 2026-10-20.

Who is affected?

According to Google, Antigravity CLI does not offer full feature parity out of the gate, but keeps the features it considers critical: Agent Skills, Hooks, Subagents and Extensions, now called plugins. Built in Go, it shares the same agent harness as the Antigravity 2.0 desktop app.

Install Antigravity CLI

The command is called agy (Antigravity).

macOS, Linux and Googlebook (binary installed at ~/.local/bin/agy):

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

Windows PowerShell (binary in C:\Users\<username>\AppData\Local\agy\bin):

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

Check the installation in a new terminal:

agy --version

On first launch, the setup asks for a color scheme and a rendering mode (full-screen buffer or inline in your terminal history).

Sign in

On launch, agy looks for a session in the operating system's secure keyring (Apple Keychain, Linux Secret Service, Windows Credential Manager). If none is found, it opens your browser: sign in with a personal Google Account (Free, Pro or Ultra plan) or choose "Business account" for a Gemini Enterprise account (Antigravity). Over SSH, the CLI gives you a URL to open manually.

Migrate your Gemini CLI setup

On first launch, if agy detects a Gemini CLI configuration, an interactive checklist offers to convert extensions and global settings and to move session tokens into the system keyring (Antigravity).

Manually, to convert Gemini extensions into Antigravity plugins:

agy plugin import gemini

The command scans the legacy local directories and converts skills, commands (turned into skills) and MCP server definitions.

What stays the same: the project's GEMINI.md and AGENTS.md context files, as well as the global ~/.gemini/GEMINI.md, are read as they are.

What changes:

Official mcp_config.json example:

{
  "mcpServers": {
    "remote-indexer": {
      "serverUrl": "https://mcp.internal.enterprise.com/sse",
      "env": {
        "AUTH_TOKEN": "secure_alpha_token"
      }
    }
  }
}

Some custom terminal themes or experimental visual overlays from Gemini CLI may not carry over. For MCP principles shared with other agents, see our guide How to set up an MCP server.

Quotas and plans

Antigravity is available to individual accounts under terms derived from Google's Terms of Service (Antigravity). All plans include Gemini models, including Gemini 3.8 Flash, as the core agent model, and access to the CLI. Limits vary:

Pro and Ultra subscribers can buy AI credits for usage beyond their quota. Google does not support bring-your-own-key (BYOK) for extra rate limits. In the CLI, /usage shows quota usage per model and /credits the credit balance (command reference).

Useful commands

Going further

Sources

Key takeaway: individual Google accounts must move to Antigravity CLI (agy), which imports extensions and MCP servers; only project skills need to be moved by hand to .agents/skills/.

Spotted an error in this article? Report it · Our corrections policy

The OrigoTech newsletter

A sourced weekly digest of AI tool news.

Read next