How to migrate from Claude Code to Gemini
aix is a CLI for defining, installing, and syncing AI editor configuration. If you are moving from Claude Code to Gemini, this guide shows what aix can carry over, what the destination editor calls each feature, and where the destination config lands.
When you are ready to run the move, aix sync claude-code --to gemini
copies the supported config from Claude Code into Gemini. Use the comparison
below first so you know which names, paths, and support differences to expect.
If you want the aix-side definitions first, review rules , prompts , mcp , skills , hooks .
How to use this guide
- Read across a row to compare the source and destination terms, support, and targets.
- Each scope line shows both what the editor supports and what aix writes today.
- Open the destination editor page at the end if you need every path, note, and terminology detail.
The biggest changes are in rules, prompts, mcp.
How to read the statuses
Support key
Editor support
- Supported The editor exposes that feature at that scope.
- No support The editor does not expose that feature at that scope.
aix support
- Native aix writes the editor's own format.
- Adapter aix keeps the feature through an adapter or alternate representation.
- No support aix does not write that feature for the destination today.
Use the Project scope and User scope rows to see where config lands at each level.
Feature comparison
| Feature | Claude Code | Gemini |
|---|---|---|
| Rules | Rules
| GEMINI.md
|
| Prompts | Commands
| Commands
|
| MCP | MCP servers
| MCP servers
|
| Skills | Skills
| Skills
|
| Agents | Subagents
| Subagents
|
| Hooks | Hooks
| Hooks
|