Gemini CLI to Antigravity CLI: Migration Steps (2026)
Google's Gemini CLI site now says that for unpaid-tier and Google One users, Gemini CLI was replaced by Antigravity CLI (agy) on June 18, 2026. If you built up a GEMINI.md, a folder of custom commands, some skills and a few MCP servers, here is what carries over and what you have to move by hand.
Everything below was checked against Google's Antigravity CLI migration guide, the Agent skills docs and the Gemini CLI custom commands docs on 2026-11-13. Both tools change quickly, so re-check anything you depend on.
The short version
| What you have in Gemini CLI | What to do for Antigravity CLI |
|---|---|
GEMINI.md and AGENTS.md in the project |
Nothing. Both are still read. |
~/.gemini/GEMINI.md (global) |
Nothing. It is still read. |
| Extensions | Run agy plugin import gemini. They become plugins. |
Project skills in .gemini/skills/ |
Move the folder to .agents/skills/. |
Global skills in ~/.gemini/skills/ |
They still load. ~/.gemini/config/skills/ is shared with the Antigravity App. |
MCP servers inside ~/.gemini/settings.json |
Move them to ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (project). |
Remote MCP url or httpUrl |
Rename the key to serverUrl. |
Loose .toml commands in .gemini/commands/ |
Turn them into skills (free script below). |
1. Your context files keep working
This is the part people worry about most, and it is the easy part. The migration guide says Antigravity CLI uses the same workspace context rules: it reads GEMINI.md and AGENTS.md in your project and your global ~/.gemini/GEMINI.md. Do not rename or rewrite them just because the tool changed.
A quick check: open a test project, start agy, and ask it to list the project rules it has loaded. Compare the answer with the file. If you need help writing a good one, see GEMINI.md examples and how to write AGENTS.md.
2. First launch offers to migrate for you
The first time you run agy on a machine with Gemini CLI settings, it shows a checklist. You pick which extensions and global settings to convert, and it moves your session tokens into your system keyring. The guide notes some custom themes and visual overlays may not carry over.
3. Extensions become plugins
agy plugin import gemini
The importer reads your installed extensions and reports, per extension, which skills, agents, commands and MCP servers it converted or skipped. Commands inside an extension are converted to skills, and bundled MCP servers go into mcp_config.json. Read that output: a skipped line means nothing was found for that part, so check it matches what you expected.
4. Move project skills to .agents/skills
The guide marks this as action required. Skills in .gemini/skills/ are not picked up as slash commands until you move them:
git mv .gemini/skills .agents/skills
Each skill is still a folder with a SKILL.md. Antigravity's frontmatter has two fields: description (required, what the skill does and when to use it) and name (optional, defaults to the folder name). The CLI turns each skill into a slash command with that name, so deploy-staging becomes /deploy-staging. After adding a skill, run /skills reload or start a new conversation. More on writing these in SKILL.md explained.
5. Move MCP servers out of settings.json
In Gemini CLI, servers lived inside ~/.gemini/settings.json. Antigravity CLI keeps them in their own file:
- Global:
~/.gemini/config/mcp_config.json - Project:
.agents/mcp_config.json
For remote servers, the URL key changed from url or httpUrl to serverUrl:
{
"mcpServers": {
"docs-search": {
"serverUrl": "https://example.com/mcp"
}
}
}
If a remote server silently stops showing up after the move, an old url key is the first thing to check.
6. Turn loose .toml commands into skills
Gemini CLI custom commands are .toml files with a required prompt and an optional description, stored in .gemini/commands/ or ~/.gemini/commands/. A file at .gemini/commands/git/commit.toml was the command /git:commit.
The migration guide describes command conversion for commands that live inside extensions. For a plain project commands folder, people are still asking on GitHub how to move them (gemini-cli issue #27325). So we wrote a small free script that does it:
Download gemini_commands_to_skills.py (MIT, Python 3.11+, no dependencies)
# preview: .gemini/commands -> .agents/skills (writes nothing)
python3 gemini_commands_to_skills.py
# write the skills
python3 gemini_commands_to_skills.py --write
# global commands
python3 gemini_commands_to_skills.py --src ~/.gemini/commands --dest ~/.gemini/config/skills --write
What it does:
git/commit.tomlbecomes the skillgit-commit, so/git:commitbecomes/git-commit.- Keeps your
description, or writes a plain one if the command had none. - Replaces
{{args}}with a note telling the agent to use whatever you typed after the slash command. - Flags
!{...}(shell output) and@{...}(file contents). Those are Gemini CLI command features. Skill docs don't describe them, so rewrite those lines as plain instructions, like "Rungit diff --stagedand read the output." - Never overwrites an existing
SKILL.md, and reports files with nopromptas errors.
Example output:
PLAN test.toml -> .agents/skills/test/SKILL.md
! {{args}} replaced with a note
PLAN git/commit.toml -> .agents/skills/git-commit/SKILL.md
! contains !{...} shell injection: rewrite as an instruction to run the command
! contains @{...} file injection: rewrite as an instruction to read the file
2 converted (dry run, add --write), 0 skipped, 1 errors
We tested it on sample commands on 2026-11-13, but we have not tested the output inside every agy version. Open one or two converted skills in agy and try them before you delete the old folder.
A migration checklist
- Commit everything first, so you can undo with git.
- Start
agyand accept the migrations you want from the checklist. - Run
agy plugin import geminiand read the report. git mv .gemini/skills .agents/skillsif you have project skills.- Move MCP servers to
mcp_config.jsonand renameurl/httpUrltoserverUrl. - Convert loose commands with the script, then fix any flagged
!{}/@{}lines. - Ask
agyto list the rules and skills it loaded, and compare with your files.
One file for every agent
Antigravity reads AGENTS.md, and so do Codex, Copilot, Cursor and many other tools. If you keep your project rules in one AGENTS.md and only put tool-specific bits in GEMINI.md or CLAUDE.md, the next tool switch is a lot less work. Our Agent Config Kit has 12 stack-specific AGENTS.md templates plus Claude, Cursor and Copilot rule files set up that way, and the free AGENTS.md generator builds a starter in your browser.
AI Coding Agent Config Kit
Instruction-file templates for 12 stacks and 12 prompts that write and audit them. 34-page PDF, $14.
Not ready to buy? Start with the free PDF.
Get 10 of our most-used prompts as a free PDF from Gumroad. You will be asked for your email so Gumroad can deliver it.