How to Migrate from Gemini CLI to Antigravity
Step-by-step migration guide from Gemini CLI to Antigravity CLI, covering configuration changes, skill compatibility, and workflow adjustments.
- 1
Audit Your Current Setup
Document your existing Gemini CLI configuration, custom skills, MCP servers, and extensions. Create a checklist of features you actively use that need to be migrated.
- 2
Install Antigravity CLI
Install Antigravity alongside your existing Gemini CLI using 'npm install -g antigravity-cli'. This allows you to run both tools during the migration period.
- 3
Migrate Configuration Files
Convert your .gemini/ directory structure to the Antigravity format. Most skills are compatible directly; configuration files need minor syntax updates documented in the migration guide.
- 4
Update MCP Server Definitions
Transfer your MCP server configurations to antigravity.config.js. The server definition format is similar but uses a different top-level structure.
- 5
Test Migrated Workflows
Run your common workflows using Antigravity to verify everything works as expected. Compare outputs with Gemini CLI to identify any behavioral differences.
- 6
Remove Gemini CLI
Once you've verified all workflows function correctly in Antigravity, uninstall Gemini CLI with 'npm uninstall -g @google/gemini-cli' and update your team's documentation.