Gemini CLI Is Shut Down: Migration Guide to Antigravity CLI (with Command Mapping)
On June 18, 2026, Google's terminal AI coding agent Gemini CLI was discontinued for free, AI Pro, and AI Ultra users. Its successor is Antigravity CLI (command name agy).
This guide covers the migration in order: install → migrate extensions → carry over settings and MCP → re-learn the commands. The command mapping tables are built by cross-checking our verified reference data for the Gemini CLI command reference (v0.50.0, 95 entries) and the Antigravity CLI (agy) command reference (v1.1.0, 105 entries).
When you need detailed descriptions and usage examples for individual commands, keep both reference pages open alongside this article. Everything here reflects Gemini CLI v0.50.0 / Antigravity CLI v1.1.0 (as of July 2026).
1. How Gemini CLI Reached End of Life
The timeline first:
| Date | Event |
|---|---|
| 2026-05-19 | Google announces Gemini CLI will be replaced by Antigravity CLI |
| 2026-06-18 | Gemini CLI discontinued for free, AI Pro, and AI Ultra users (EOL) |
| 2026-07-08 | Antigravity CLI v1.1.0 released (mode cycling generally available, /planning renamed to /plan, /fast removed) |
One important nuance: Gemini CLI did not vanish entirely. For Gemini Code Assist Standard / Enterprise customers, v0.50.0 remains available as a maintained stable release. New feature development has moved to Antigravity CLI, though — so for individual developers, migrating to agy is the practical path forward.
2. What Is Antigravity CLI (agy)?
Antigravity CLI is Google's AI coding agent for the terminal, offering multi-step reasoning, multi-file edits, tool calls, and persistent conversation history.
Coming from Gemini CLI, these are the four things worth knowing up front:
- Interactive TUI plus non-interactive mode:
agystarts an interactive session;agy -p "prompt"runs once and prints the result to stdout (for CI and scripting) - Designed to inherit your Gemini CLI assets: settings live under the same
~/.geminidirectory (~/.gemini/antigravity-cli/), your GEMINI.md context file is read as-is, and extensions can be converted withagy plugin import gemini - Permission presets: tool approval is governed by four presets —
request-review(default) /proceed-in-sandbox/always-proceed/strict— switchable via/permissions - Not the same thing as Antigravity IDE: the IDE is a GUI editor product; the CLI (
agy) is a terminal tool. This article covers the CLI
3. Migration Steps (4 Steps)
Step 1: Install
# macOS / Linux (the binary is placed at ~/.local/bin/agy)
curl -fsSL https://antigravity.google/cli/install.sh | bash
# Windows (PowerShell)
irm https://antigravity.google/cli/install.ps1 | iex
After installing, run agy install to configure your PATH and shell settings. Add --skip-aliases to keep existing agy / antigravity aliases, or --skip-path to leave your shell profile's PATH untouched.
Step 2: Launch and Verify
Run agy to start an interactive TUI session, then check your environment:
| Command | What it shows |
|---|---|
agy models |
Available models |
agy changelog |
Release notes (changelog) |
/credits (inside the TUI) |
Remaining AI credits and usage |
Step 3: Migrate Extensions
If you used Gemini CLI extensions (managed via /extensions), there is a dedicated migration command:
agy plugin import gemini
This converts your Gemini CLI extensions into Antigravity plugins. From then on, manage them with agy plugin list / enable / disable / uninstall. Think of it as the TUI's /extensions having moved to the agy plugin CLI subcommand.
Step 4: Check Context and Settings
- GEMINI.md: no rewrite needed — agy reads it as-is. If you want instructions shared across multiple AI agents, consolidating into the standard AGENTS.md format is an option
- settings.json: your new user settings file is
~/.gemini/antigravity-cli/settings.json(details in §5) - MCP servers: re-declare them in agy's config files (details in §5)
4. Command Mapping (Gemini CLI → agy)
The tables below are based on the entries in both references (v0.50.0 / v1.1.0). "No equivalent" reflects the v1.1.0 state.
Launching, Sessions, and Conversations
| You want to… | Gemini CLI | Antigravity CLI | Notes |
|---|---|---|---|
| Start an interactive session | gemini |
agy |
|
| Run once, non-interactively | gemini -p "..." |
agy -p "..." |
agy's long form is --print; for CI and scripts |
| Run a prompt, then stay interactive | -i, --prompt-interactive |
-i, --prompt-interactive |
Same name |
| Resume the latest session | --resume (-r) |
-c, --continue |
|
| Resume a specific session | --session-id / --list-sessions |
--conversation / /resume |
agy lists sessions in the TUI via /resume (alias /switch) |
| Browse and resume past conversations | /resume (alias /chat) |
/resume (aliases /switch, /conversation) |
Nearly identical |
| Rewind the conversation | /rewind |
/rewind (alias /undo) |
|
| Quit | /quit (/exit) |
/exit |
Models and Execution Modes
| You want to… | Gemini CLI | Antigravity CLI | Notes |
|---|---|---|---|
| Switch models (in the TUI) | /model |
/model |
|
| Pick a model at launch | --model (-m) |
--model |
|
| Plan mode | /plan |
/plan |
agy renamed /planning to /plan in v1.1.0 (/fast was removed) |
| Cycle modes | Shift+Tab (approval modes) |
Shift+Tab (default → accept-edits → plan) |
Generally available in agy v1.1.0 |
| Set the mode at launch | --approval-mode |
--mode |
agy accepts default / accept-edits / plan |
| Auto-approve everything | --yolo (-y) / Ctrl+Y |
--dangerously-skip-permissions |
No in-TUI toggle; use /permissions → always-proceed instead |
| Sandboxed execution | --sandbox (-s) |
--sandbox |
agy can also enforce it via enableTerminalSandbox in settings.json |
Context and Workspace
| You want to… | Gemini CLI | Antigravity CLI | Notes |
|---|---|---|---|
| Add a directory (in the TUI) | /directory add |
/add-dir |
|
| Add directories at launch | --include-directories |
--add-dir |
agy allows repeating the flag |
| Context files | GEMINI.md (managed via /memory, generated via /init) |
GEMINI.md / AGENTS.md | GEMINI.md keeps working as-is; there is no /memory or /init equivalent |
| Clear the screen | /clear or Ctrl+L |
Ctrl+L |
agy's /clear also resets the conversation context (see §6) |
| Run a shell command | !<command> |
!<command> |
e.g. !npm test |
| Check background work | /shells |
/tasks |
agy shows shell execution logs in the task manager panel |
Settings and Management
| You want to… | Gemini CLI | Antigravity CLI | Notes |
|---|---|---|---|
| Settings editor | /settings |
/config |
agy keeps /settings as an alias, so the old name still works |
| Change the theme | /theme |
colorScheme in settings.json |
Default: terminal |
| External editor | /editor |
editor in settings.json |
Default auto (respects $EDITOR) |
| Change auth | /auth |
/logout, then re-authenticate |
|
| Permissions | /permissions (folder trust) |
/permissions (permission presets) |
Same name, different job (see §6) |
| Hooks | /hooks |
/hooks |
|
| MCP servers | /mcp |
/mcp |
|
| Subagents | /agents |
/agents |
|
| Agent Skills | /skills |
/skills |
|
| Extensions | /extensions, --extensions |
agy plugin install / list / enable / disable |
Migrate with agy plugin import gemini |
| Usage stats | /stats |
/credits |
agy opens the credits panel (remaining credits and usage) |
| Documentation | /docs (opens the browser) |
/usage (offline manual) |
agy's /usage is the manual, not usage stats (see §6) |
| Version info | /about, --version |
agy changelog |
Shown as release notes |
| Help | /help, ? |
? (on an empty prompt), agy help |
Commands with No Equivalent
The following Gemini CLI commands have no direct counterpart in agy as of v1.1.0:
- With a workaround:
/restore(no file-restore command; rewind the conversation with/rewindinstead),/terminal-setup(unnecessary — agy supportsShift+Enter/Ctrl+Jnewlines out of the box),--debug(set the log destination with--log-fileand output volume with theverbositysetting) - No equivalent:
/vim,/copy,/compress,/tools,/bug,/privacy,/upgrade,/ide,/setup-github,--worktree,--acp,--output-format,--screen-reader,--policy,--admin-policy,--skip-trust
5. Migrating Settings Files and MCP Config
agy keeps its configuration under the same ~/.gemini directory Gemini CLI used. Here is the map:
| Item | Path | Notes |
|---|---|---|
| User settings | ~/.gemini/antigravity-cli/settings.json |
Theme, permission behavior, etc.; also editable via /config |
| Keybindings | ~/.gemini/antigravity-cli/keybindings.json |
Editable via /keybindings; delete the file to restore defaults |
| MCP config (global) | ~/.gemini/config/mcp_config.json |
MCP servers shared across projects |
| MCP config (workspace) | .agents/mcp_config.json |
Per-project MCP servers |
| Context instructions | GEMINI.md / AGENTS.md |
GEMINI.md works unchanged from Gemini CLI |
Two migration points:
- Re-declare your MCP servers: MCP servers you used with Gemini CLI go into
~/.gemini/config/mcp_config.json(global) or.agents/mcp_config.json(per project). Check and manage connections in the TUI's/mcppanel - Do not delete
~/.geminiwholesale: if you remove the whole~/.geminidirectory while "cleaning up" Gemini CLI, you also wipe agy's own settings underneath it (antigravity-cli/andconfig/)
The most useful settings.json keys (all editable from the /config editor):
| Key | Default | Purpose |
|---|---|---|
toolPermission |
request-review | Tool approval behavior (permission preset) |
artifactReviewPolicy |
asks-for-review | Review flow for generated code |
colorScheme |
terminal | Color theme |
editor |
auto | External editor launched by Ctrl+G etc. |
enableTerminalSandbox |
false | Sandboxed command execution |
notifications |
false | Desktop notification / bell on task completion |
6. Gotchas: Same Name, Different Behavior
What actually trips people up during migration is not the removed commands — it's the operations that kept their name or key but changed behavior. Five to remember:
/clearwipes your context: in Gemini CLI,/clearonly cleared the screen. In agy,/clearalso resets the conversation context. To just tidy the screen, useCtrl+L/usageopens the manual: if you type it expecting usage stats, you get the offline developer manual. Remaining credits and usage live in/creditsCtrl+Rchanged meaning: reverse history search in Gemini CLI, but in agy it opens the artifact review panel. Walk input history withUp/Downinstead (Ctrl+P/Ctrl+Nare gone too)Ctrl+Kno longer kills to end of line: in agy,Ctrl+Kfast-path-approves the pending subagent. Pressing it out of Emacs habit performs an approval you may not have intended/permissionshas a different job: folder trust management in Gemini CLI, but in agy it switches the permission preset (request-review / proceed-in-sandbox / always-proceed / strict)
On the flip side, these agy additions are worth learning:
| Operation | What it does |
|---|---|
/fork (alias /branch) |
Fork the current session into a parallel one |
/btw |
Ask a side question without interrupting the main conversation |
/diff |
Show a unified diff of changed files |
f (v1.1.0) |
Review and accept/reject individual code changes in the request-review diff preview |
Ctrl+Z / Ctrl+Shift+Z |
Undo / redo prompt edits |
Alt+J |
Focus the next subagent awaiting approval |
FAQ
Is Gemini CLI completely unusable now?
It was discontinued for free, AI Pro, and AI Ultra users on June 18, 2026. For Gemini Code Assist Standard / Enterprise customers, v0.50.0 remains available as a maintained stable release. Since feature development has moved to Antigravity CLI, migrating to agy is the practical choice for individual use.
Do I need to rewrite GEMINI.md?
No. Antigravity CLI reads your workspace GEMINI.md as-is for context instructions. If you want instructions shared across multiple AI agents, consider consolidating into the standard AGENTS.md format.
Can I keep using my Gemini CLI extensions?
Run agy plugin import gemini to convert Gemini CLI extensions into Antigravity plugins. Afterwards, check them with agy plugin list and manage them with enable / disable / uninstall.
Can I carry over my Gemini CLI conversation history?
There is no import command for it (as of v1.1.0) — agy plugin import gemini only migrates extensions. Conversation history in agy accumulates fresh, and you resume it with /resume or -c, --continue.
What replaces --yolo?
At launch, agy --dangerously-skip-permissions; during a session, switch the permission preset to always-proceed via /permissions. Both skip safety confirmations, so pairing them with a sandbox (the proceed-in-sandbox preset or --sandbox) is recommended.
Are Antigravity IDE and Antigravity CLI the same product?
No. Antigravity IDE is a GUI editor product, while Antigravity CLI (agy) is a command-line tool that runs in your terminal. This article covered the CLI migration.
Summary
- Gemini CLI ended for free and AI Pro/Ultra users on 2026-06-18; for individual developers the migration target is Antigravity CLI (
agy) - The core of the migration is three moves: install →
agy plugin import gemini→ re-declare MCP servers. GEMINI.md keeps working as-is - Many commands migrate by name (
/model,/mcp,/agents, …), but/clear,/usage,/permissions,Ctrl+R, andCtrl+Kbehave differently — watch out for those
For the full command lists with detailed descriptions and examples, see our verified, maintained references:
- Google Antigravity CLI (agy) command reference — all 105 entries: CLI subcommands, flags, slash commands, shortcuts, and settings
- Gemini CLI command reference — all 95 entries for v0.50.0 (the continued Code Assist release)