Support keyword: gemini cli to antigravity cli

Gemini CLI to Antigravity CLI migration

Move carefully: the real task is not only installing the new CLI, but checking skills, settings, MCP servers, hooks, and context files before Gemini CLI access changes.

Updated on 2026-05-26. Independent guide. Use official Google links for downloads and account actions.

Why migration matters now

Google announced on May 19, 2026 that Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for Google AI Pro and Ultra, and for free individual Gemini Code Assist users, on June 18, 2026. That date is the reason migration searches are rising. Enterprise and paid API-key scenarios have separate rules, so do not assume every organization must move the same way.

The practical migration job is to avoid losing the workflows you built around Gemini CLI: skills, commands, MCP servers, context files, keybindings, and permission expectations.

Migration checklist

  1. Install Antigravity CLI from the official Google source.
  2. Open the official migration guide and run the supported import or onboarding flow where available.
  3. Check global and workspace skills. Workspace-specific skills may need to move into .agents/skills.
  4. Review MCP server configuration. Antigravity CLI uses its own MCP configuration path and remote-server fields can differ.
  5. Keep GEMINI.md and AGENTS.md context files visible in the active workspace.
  6. Run a safe prompt that reads files but does not write. Then run a controlled edit in a disposable branch.
  7. Document any Gemini CLI behavior that does not have feature parity yet.

What not to migrate blindly

Do not copy stale permission shortcuts into a new agent environment without reviewing them. Do not assume every command maps 1:1. Do not delete old settings until the new CLI can handle your daily tasks. If you use enterprise credentials, check the Google transition post and your organization's policy before changing production workflows.

Sources: official Google Antigravity product pages, Google Antigravity CLI documentation, and the Google Developers transition announcement. This site is an independent guide and is not affiliated with Google.

FAQ

Is there a June 18, 2026 deadline?

Google's transition post names June 18, 2026 for individual and free consumer usage changes. Enterprise cases have separate handling.

Do Gemini CLI skills still matter?

Yes. The migration docs indicate skills and related customizations are part of the migration surface, but locations and management can differ.

Is migration checklist the main keyword?

No. It is a support page under the broader antigravity cli cluster.

Related Antigravity CLI pages