Based on Google’s official docs, checked October 20, 2026

How to migrate from Gemini CLI to Antigravity CLI

Antigravity CLI, started with the agy command, keeps the main building blocks of Gemini CLI: context files, skills and MCP servers. Most of the move is automatic, but a few paths and one MCP field changed, and project skills need a manual move. This checklist follows Google’s official migration page as checked on October 20, 2026.

1. 1. Run agy once and accept onboarding

   The first time you run agy on a machine with Gemini CLI configuration, Antigravity CLI detects your existing profiles and shows a checklist. Pick the extensions and global settings to convert. Your session tokens move into the operating system keyring, and default display settings carry over.

   agy

2. 2. Convert Gemini CLI extensions to plugins

   Antigravity calls extensions plugins. The import command finds your local Gemini extensions, reads their manifests and converts them. Its report shows what moved for each extension: skills, agents, legacy commands (converted into skills) and MCP server definitions (moved into mcp_config.json).

   agy plugin import gemini

3. 3. Keep GEMINI.md and AGENTS.md as they are

   No changes are needed. Antigravity CLI still reads GEMINI.md and AGENTS.md in your project and your global ~/.gemini/GEMINI.md.

4. 4. Move project skills to .agents/skills/

   This is the one step that needs a manual change. Project skills in .gemini/skills/ are not picked up until you rename or move the folder to .agents/skills/. Personal skills move from ~/.gemini/skills/ to ~/.gemini/antigravity-cli/skills/.

   mkdir -p .agents && git mv .gemini/skills .agents/skills

5. 5. Move MCP servers into mcp_config.json

   Gemini CLI kept servers inside ~/.gemini/settings.json. Antigravity CLI reads ~/.gemini/config/mcp_config.json for global servers and .agents/mcp_config.json for project servers. For remote servers, rename url or httpUrl to serverUrl.

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

6. 6. Check the result

   Type /mcp in Antigravity CLI to see whether each server connects, and run one of your skills as a slash command to confirm it was found.

What changes, at a glance

Context files: GEMINI.md, AGENTS.md and ~/.gemini/GEMINI.md work unchanged.

Extensions become plugins, through onboarding or agy plugin import gemini.

Global skills: ~/.gemini/skills/ becomes ~/.gemini/antigravity-cli/skills/.

Project skills: .gemini/skills/ becomes .agents/skills/. You have to move these yourself.

MCP servers: ~/.gemini/settings.json becomes ~/.gemini/config/mcp_config.json (global) and .agents/mcp_config.json (project).

Remote MCP servers: url and httpUrl become serverUrl.

Sign-in: session tokens move into the OS keyring during onboarding.

What may not carry over

Google says parity is partial. Workspace skills, rules and MCP servers are supported, but some custom terminal themes and experimental visual overlays from Gemini CLI might not be. Expect to set your theme and keybindings again in the new settings.

Why the .agents/ folder matters beyond Antigravity

The .agents/skills/ folder is not unique to Antigravity. Codex, Cursor and GitHub Copilot also read skills from .agents/skills/, so moving your Gemini skills there can make them usable in more than one agent. Our portable skills guide explains which agents read which folders.

After the move: permissions

Antigravity CLI has its own permission system, configured in ~/.gemini/antigravity-cli/settings.json with allow, deny and ask lists. If the agent keeps asking before commands or MCP tools, see the permissions section of our Antigravity MCP guide.

Tips

• Commit the .gemini/skills to .agents/skills rename so your teammates get it too.
• Search your MCP config for "url" and "httpUrl" after converting; remote servers fail without serverUrl.
• Keep secrets out of a project .agents/mcp_config.json that you commit.

Next steps

Sources

• https://antigravity.google/docs/cli/gcli-migration/ · checked 2026-10-20
• https://antigravity.google/docs/permissions/ · checked 2026-10-20