Table of Contents
Overview
As of June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extension stopped processing requests for personal-use tiers. For developers who'd been using Gemini CLI as part of their daily routine, migrating to its successor, "Antigravity CLI," has become unavoidable.
What happened
Google announced it was ending Gemini CLI for personal users and shifting them to Antigravity CLI. Antigravity CLI is designed around running multiple agents in parallel and asynchronous workflows, and is said to support running several tasks side by side rather than just handling one-off conversational assistance.
What carries over, and what doesn't
An important part of the migration is knowing what carries over as-is and what requires manual reconfiguration. GEMINI.md (a per-project configuration file) and globally configured Agent Skills reportedly migrate over as-is. Workspace-level Skills, Extensions, and MCP server settings, on the other hand, apparently require manual reconfiguration.
The concrete migration steps
The actual migration process broadly looks like this:
- Install Antigravity CLI. On macOS/Linux, run the official install script with a single line in the terminal; on Windows, run the equivalent install script from PowerShell
- A browser will automatically open on first launch — complete login (OAuth) with your Google account
- Run the command "agy plugin import gemini" to convert the extensions and settings you were using in Gemini CLI into the new plugin format
- Run "agy doctor" to confirm your environment is set up correctly
The order matters here. It's said to go more smoothly if you finish installing and importing into Antigravity CLI first, and only uninstall the old Gemini CLI afterward. Doing it in the reverse order risks the config files you need to reference getting deleted first, which could cause the import to fail.
Common stumbling points
A commonly reported stumbling point during migration is the "agy" command not being recognized. In this case, restart your terminal and check whether your PATH is set up correctly. If you hit an error while running the migration command, the first thing to check is whether the old Gemini CLI's config files ("~/.config/gemini-cli/" or "~/.gemini/") are corrupted or simply missing. It's also pointed out that migration tends to fail less because of the install itself, and more because old settings, automation scripts, or team rules get left behind unaddressed.
How the community has reacted
Reactions to this migration within the developer community seem mixed. Antigravity CLI is a closed-source tool written in Go, and compared to the relatively open-source-leaning Gemini CLI, some developers reportedly feel it's a step backward. Before going ahead with the migration, it's worth checking in advance whether your own development workflow is genuinely covered by Antigravity CLI.
A real case of migrating and building with it
In one case of actually migrating from Gemini CLI to Antigravity CLI and building an app for Cloud Run, the developer reportedly found that, because Antigravity CLI supports running multiple agents in parallel, it handled noticeably larger tasks thrown at it in one go without breaking down, compared to the Gemini CLI era.
Summary: a pre-migration checklist
If you're about to migrate away from Gemini CLI, check the following:
- GEMINI.md and global Agent Skills migrate over as-is
- Workspace-level Skills, Extensions, and MCP settings need manual reconfiguration
- If the "agy" command isn't recognized, restart your terminal and check your PATH
- If a migration error occurs, check the location and existence of your old config files
- Don't forget to also take stock of old automation scripts and team rules
A tool's shutdown always seems to arrive suddenly, but keeping these points in mind ahead of time should let you get through the migration without panicking.