# Antigravity CLI migration from Gemini CLI

A migration checklist for Gemini CLI users moving to Antigravity CLI, with the key dates, retained concepts, and verification steps.

## Quick Answer

Treat the move from Gemini CLI to Antigravity CLI as a workflow migration, not only a package rename. Preserve commands, auth assumptions, agent skills, hooks, extensions, and CI usage in a checklist before switching teams over.

## Best for

Developers and teams using Gemini CLI or Google coding agents.

## Use this guide to

Gemini CLI users need to understand what changes when moving to Antigravity CLI.

## Recommended play

1. Treat the migration as a workflow compatibility audit, not a copy update.
2. Check official Google dates and changed behaviors before each rollout step.
3. Keep the setup and security checks close to the migration checklist so teams can verify permissions, credentials, and automation together.

## Gemini CLI to Antigravity CLI migration map

Use this map to find the pieces most likely to break when a team moves command-line agent workflows.

| Area | Check area | What to compare | Risk if skipped |
| --- | --- | --- | --- |
| Commands | Local and CI command surface | Local scripts, CI jobs, shell aliases, onboarding docs | Old command paths keep failing after the team switches |
| Authentication | Access and credential model | Personal login, enterprise access, service accounts, environment variables | Users cannot reproduce the workflow outside one machine |
| Extensions and hooks | Automation compatibility | Custom integrations, lifecycle hooks, editor extensions | Automation silently stops or runs at the wrong moment |
| Agent behavior | Runtime behavior | Skills, subagents, context rules, model defaults | The new CLI behaves differently even when commands look similar |

## Execution steps

1. **Freeze current Gemini CLI usage** — Capture commands, scripts, docs, CI references, auth assumptions, and plugin or extension usage before editing anything.
2. **Map each workflow** — For every recurring workflow, write the Antigravity CLI equivalent and mark unresolved behavior differences.
3. **Run a small migration test** — Move one repository or one workflow first, verify auth and hooks, then update docs before expanding to the team.
4. **Monitor official updates** — Keep a dated change log on the page so users can see what changed after the migration article was first published.

## Common pitfalls

- **Renaming commands without testing workflow behavior**: Verify auth, extensions, hooks, and CI outputs before declaring the migration complete.
- **Ignoring old docs and onboarding paths**: Update internal docs, README snippets, and developer onboarding at the same time as scripts.
- **Letting a time-sensitive page age silently**: Add a review date and update the page when Google changes migration details.

## Implementation checklist

- [ ] Inventory Gemini CLI commands used locally and in CI.
- [ ] Map each command to Antigravity CLI behavior.
- [ ] Confirm authentication and enterprise access.
- [ ] Retest hooks, skills, extensions, and subagents.
- [ ] Update internal docs and onboarding.
- [ ] Monitor Google docs for deadline or feature changes.

## FAQ

**Q: What should you do first?**

Treat the migration as a workflow compatibility audit, not a copy update.

**Q: Who is this guide for?**

Developers and teams using Gemini CLI or Google coding agents.

**Q: What evidence supports this guide?**

This guide uses listed source material from Google. Source links and scope notes are available on this page.

## Evidence sources

- [Transitioning Gemini CLI to Antigravity CLI](https://developers.googleblog.com/en/an-important-update-transitioning-gemini-cli-to-antigravity-cli/) — Google. Official transition announcement.
- [Antigravity CLI migration documentation](https://www.antigravity.google/docs/gcli-migration) — Google. Official migration reference.

## Related guides

- [hooks and MCP setup guide](/guides/claude-code-hooks-mcp-setup) — Migration readers often need a broader control map for hooks, skills, and external tooling.
- [subagents workflow examples](/guides/claude-code-subagents-examples) — Teams comparing CLI behavior also need a way to decide when parallel agent workflows are useful.

---
Canonical: https://www.kyenai.com/guides/antigravity-cli-gemini-cli-migration