newspaperPress Guidelines
Pricing
Blog
Downloaddownload

Explore our next generation products

See overview

Products

antigravityAntigravity 2.0terminalAntigravity CLIcodeAntigravity IDEsdkAntigravity SDK

Built for developers in the agent-first era

See overview
EnterpriseFrontendFullstackScienceMarketer

Everything you need to stay up-to-date and get help

Documentationkeyboard_arrow_rightChangelogSupportPressReleases

Explore our next generation products

See overview

Products

antigravityAntigravity 2.0terminalAntigravity CLIcodeAntigravity IDEsdkAntigravity SDK

Built for developers in the agent-first era

See overview
EnterpriseFrontendFullstackScienceMarketer
Pricing
Blog

Everything you need to stay up-to-date and get help

Documentationkeyboard_arrow_rightChangelogSupportPressReleases
Home
Antigravity 2.0v2.3.1keyboard_arrow_right
Overview
Getting Started
Build with Google
Feature Overview
Models
Projects
Settingskeyboard_arrow_right
Overview
Agent Settings
Artifact Review
Customizationskeyboard_arrow_right
MCP
Skills
Rules
Plugins
Hooks
Sidecars
Agent Capabilitieskeyboard_arrow_right
Permissions
Subagents
Artifactskeyboard_arrow_right
Overview
Plan
Walkthrough
Screenshots
Antigravity CLIv1.1.5keyboard_arrow_right
Overview
Getting Started
Installation & Auth
Tutorial
Using AGY CLI
Features
Gemini Migration
Prompting
Artifactskeyboard_arrow_right
Overview
Conversations
Agent Capabilitieskeyboard_arrow_right
Choose an execution mode
Subagents
Sandbox
Permissions
Projects
Settingskeyboard_arrow_right
Overview
AI Credits
Customizationskeyboard_arrow_right
MCP
Plugins & Skills
Status Line
Window Title
Commandskeyboard_arrow_right
Agents (/agents)
Code Search (/codesearch)
AI Credits (/credits)
Diff (/diff)
Permissions (/permissions)
Resume (/resume)
Status Line (/statusline)
Window Title (/title)
Model Quotas (/usage, /quota)
Best Practices
Troubleshooting
Reference
Antigravity SDKv0.1.7keyboard_arrow_right
Overview + Quick Start
Customizationskeyboard_arrow_right
MCP
Antigravity IDEv2.1.1keyboard_arrow_right
Overview
Getting Started
Featureskeyboard_arrow_right
Tab
Side Panel
Review Changes
Artifactskeyboard_arrow_right
Plan
Walkthrough
Screenshots
Browser Recordings
Browserkeyboard_arrow_right
Overview
Allowlist / Denylist
Separate Chrome Profile
Customizationskeyboard_arrow_right
MCP
Skills
Rules
Workflows
Plugins
Hooks
Settings
Migrationkeyboard_arrow_right
Firebase Studio Migration
Enterprise
Plans
FAQ
  • side_navigation
  • Antigravity CLI
  • >
  • Gemini Migration

Migrating from Gemini CLIlink

Convert your legacy configurations, import Gemini CLI extensions as native plugins, adapt custom skills paths, and reformat Model Context Protocol configurations.

Overviewlink

Antigravity CLI preserves backward compatibility with the core developer-experience constructs popularized by Gemini CLI. To ensure a seamless upgrade, the CLI offers automatic onboarding conversion alongside explicit CLI migration command sequences.

First-launch onboardinglink

When you execute agy for the first time in an environment containing legacy configurations, the CLI automatically detects your existing profiles. An interactive checklist prompts you to choose which assets to migrate:
  1. Auto-conversion: Select the extensions and global configurations you wish to convert.
  2. Keyring storage: The CLI migrates your active session tokens securely into your operating system's native keyring storage.
  3. Settings alignment: Default visual parameters and rendering buffers map automatically to your new settings profile.
info
Partial Parity: While we preserve support for workspace skills, rules, and MCP servers, certain customized terminal themes or experimental visual overlays from Gemini CLI may not be supported.

Converting extensions to pluginslink

Since Gemini CLI launched, the industry has standardized on the term plugins. You can manually convert your legacy Gemini extensions to native Antigravity plugins by executing:
bash
agy plugin import gemini
This utility searches your legacy local directories, parses your extension manifests, and converts files into native layout blocks.

Expected import outputlink

text
[ok]   conductor-tools
       - skills     : skipped (none detected)
       - agents     : skipped (none detected)
       ✔ commands   : 4 legacy commands converted to skills
       - mcpServers : skipped (none detected)
[ok]   google-workspace
       ✔ skills     : 5 skills processed
       - agents     : skipped (none detected)
       ✔ commands   : 2 legacy commands converted to skills
       ✔ mcpServers : 1 server definition migrated to mcp_config.json

Context files and workspace ruleslink

Both CLI platforms utilize identical workspace context rules. No modifications are needed to your existing rule documents:
  • Workspace local context: The agent continues to parse and enforce rule constraints defined inside your active directory's GEMINI.md and AGENTS.md files.
  • Global developer context: The agent automatically consults and enforces your global constraints located at ~/.gemini/GEMINI.md.

Updated skills pathslink

While global shared skills remain in your user home directory, the target folder path for local workspace-specific skills has been updated.
ConfigurationGemini CLIAntigravity CLI
Global shared path~/.gemini/skills/~/.gemini/antigravity-cli/skills/
Workspace project path.gemini/skills/.agents/skills/
warning
Action Required: If your project contains custom workspace skills defined in .gemini/skills/, you must manually rename or relocate the folder to .agents/skills/ for the Antigravity agent to recognize them as active slash commands.

MCP config formatting changeslink

Antigravity CLI separates Model Context Protocol servers into dedicated, lightweight JSON profiles instead of nesting them inside your primary preferences configuration.

Directory mappinglink

  • Legacy Gemini Config: Servers were declared inline within ~/.gemini/settings.json.
  • Antigravity CLI Config: Servers are defined inside a standalone mcp_config.json profile:
  • Global servers: ~/.gemini/config/mcp_config.json
  • Workspace servers: .agents/mcp_config.json

Required schema updateslink

When manually migrating remote websocket or SSE server definitions, update the URI key parameter to match the current standard:
  • Legacy schema keys: url or httpUrl
  • Modern schema key: serverUrl
json
{
  "mcpServers": {
    "remote-indexer": {
      "serverUrl": "https://mcp.internal.enterprise.com/sse",
      "env": {
        "AUTH_TOKEN": "secure_alpha_token"
      }
    }
  }
}

Next stepslink

Begin configuring your new visual parameters and troubleshooting any setup anomalies:
  • Settings, Rendering & Keybindings: Customize keyboard hotkeys, themes, and screen buffers.
  • Troubleshooting: Learn how to resolve authentication lockouts or path issues.
  • CLI Reference: Access standard parameters lists and slash command mappings.
Features
Prompting & Interaction
On this Page
Migrating from Gemini CLIOverviewFirst-launch onboardingConverting extensions to pluginsContext files and workspace rulesUpdated skills pathsMCP config formatting changesNext steps