Gemini CLI Is Ending June 18: Complete Migration Guide to Antigravity CLI
Gemini CLI stops serving requests on June 18, 2026. Google announced the transition to Antigravity CLI (agy) on May 19 — here is everything you need to migrate before the deadline.
gemini command) stops responding for Google AI Pro, Ultra, and individual free-tier users. Enterprise customers have a separate extended timeline. The new command is agy. Antigravity CLI has been GA since May 19, 2026.gemini with agy in all scripts and aliases. Your Hooks, Subagents, and Agent Skills migrate unchanged. Extensions are now called plugins. The free tier (1,000 req/day) ends — Antigravity requires a Google AI Pro subscription. Gemini CLI was Apache 2.0 open source; Antigravity CLI is not. The 1M token context window is retained.
What Happened to Gemini CLI
Gemini CLI launched in mid-2025 as a free, open-source terminal coding agent powered by Gemini 2.5 Pro. It was notable for two things that set it apart from Claude Code and Codex CLI: a genuinely generous free tier (1,000 requests/day with a Google account) and a 1 million token context window — five times larger than Claude Code's 200K limit.
On May 19, 2026, at Google I/O 2026, Google announced Antigravity 2.0 — a full agent-first development platform to compete directly with Cursor and Claude Code. The platform includes a VS Code fork (the Antigravity IDE), the Antigravity CLI (agy), an SDK, and Managed Agents in the Gemini API.
Google's message to Gemini CLI users in the transition announcement was direct: "your workflows have simply outgrown those early days of 2025." Gemini CLI was reframed as an early experiment; Antigravity CLI is positioned as the production-grade successor and Google's "premier agent-first development platform."
June 18 Deadline: What Stops Working
On June 18, 2026, Gemini CLI stops serving requests for the following user groups:
- Google AI Pro subscribers (formerly Google One AI Premium) — must migrate to Antigravity CLI
- Google AI Ultra subscribers — must migrate to Antigravity CLI
- Individual free-tier users (1,000 req/day Google account login) — must migrate to a paid Google AI plan and Antigravity CLI
After June 18, running gemini in your terminal will fail. If you have shell scripts, GitHub Actions, CI/CD pipelines, MCP configurations, or tmux session launchers that call gemini, they will break. The migration window is short — audit your toolchain now.
What Changes in Antigravity CLI
| Dimension | Gemini CLI (old) | Antigravity CLI (new) |
|---|---|---|
| CLI command | gemini | agy |
| Extensions | Extensions (~/.gemini/extensions/) | Plugins (renamed, new path) |
| Open source | ✔ Apache 2.0 (GitHub) | ✘ Closed source |
| Free tier | 1,000 req/day (Google account) | Requires Google AI Pro/Ultra plan |
| Underlying model | Gemini 2.5 Pro / Flash | Gemini 3.5 Flash / Pro |
| IDE integration | Gemini Code Assist (VS Code extension) | Antigravity IDE (VS Code fork) |
| Config directory | ~/.gemini/ | ~/.antigravity/ (verify against docs) |
| Custom commands | ~/.gemini/commands/*.toml | Updated format (see docs) |
gemini to agy. This is a one-line find-and-replace in most scripts, but it will break any automation that calls the old binary name.
What Stays the Same
Google confirmed that the following Gemini CLI capabilities are fully retained in Antigravity CLI:
| Feature | Status in Antigravity CLI |
|---|---|
| Agent Skills | ✔ Fully retained, same format |
| Hooks | ✔ Fully retained, same format |
| Subagents | ✔ Fully retained, same orchestration model |
| 1M token context window | ✔ Retained (Gemini 3.5 models) |
| Multi-turn interactive sessions | ✔ Same interactive workflow |
File injection (@ prefix) | ✔ Retained |
Shell passthrough (! prefix) | ✔ Retained |
| Slash commands | ✔ Retained (verify specific commands) |
Google explicitly noted that "there won't be a 1:1 feature parity on day one" — some Gemini CLI-specific features may arrive in Antigravity CLI in later releases. Check the official transition announcement and Antigravity CLI docs for the current feature parity table.
Step-by-Step Migration Guide
1Install Antigravity CLI
Antigravity CLI has been available to all users since May 19, 2026. Install it via the official installer or your package manager:
# macOS (Homebrew)
brew install google-antigravity/tap/agy
# Linux (direct install)
curl -fsSL https://dl.antigravity.google/install.sh | sh
# Verify installation
agy --version
See the official installation docs for the latest method — install paths may change before June 18.
2Authenticate with your Google AI account
Antigravity CLI requires a Google AI Pro or Ultra subscription (the individual free tier ended with Gemini CLI). Sign in to link your account:
# Interactive login
agy auth login
# Verify your session
agy auth status
If you don't have a Google AI Pro subscription, you'll need to sign up at ai.google before proceeding.
3Update shell scripts and aliases
This is the most critical step. Find every occurrence of the gemini command across your scripts, aliases, and CI/CD configs:
# Find all scripts calling 'gemini'
grep -r "gemini" ~/.zshrc ~/.bashrc ~/.profile ~/scripts/ .github/ 2>/dev/null
# Bulk replace in scripts (macOS)
find ~/scripts -name "*.sh" -exec sed -i '' 's/\bgemini\b/agy/g' {} +
# Update shell aliases
# Change: alias g='gemini'
# To: alias g='agy'
Also check: GitHub Actions workflows, Makefile targets, Dockerfile RUN commands, and any cron jobs that invoke Gemini CLI.
4Migrate Extensions to Plugins
Gemini CLI Extensions are now called Plugins in Antigravity CLI. The extension directory and configuration format have changed. For each extension you used:
# Gemini CLI (old)
ls ~/.gemini/extensions/
# Antigravity CLI (new) — verify exact path in docs
ls ~/.antigravity/plugins/
Check the Antigravity CLI plugins documentation for the updated manifest format. Simple extensions (no binary dependencies) typically migrate by renaming the config file; complex extensions may need updates.
5Migrate custom TOML commands
If you used Gemini CLI's custom command feature (~/.gemini/commands/*.toml, released July 2025), verify the new path and format for Antigravity CLI:
# Gemini CLI custom commands (old)
ls ~/.gemini/commands/
# Move and verify format
# Check: https://antigravity.google/docs/cli/commands
The TOML-based command format may have been updated. Test each custom command interactively with agy after copying.
6Test your core workflows
Validate that your most-used workflows function in Antigravity CLI before the June 18 deadline:
# Test interactive session
agy
# Test non-interactive (headless) mode
agy -p "Summarize the changes in the last 5 commits"
# Test with file injection
agy -p "Review this file" @src/main.py
# Test subagent invocation (if you use them)
agy --agent-skills
Run this at least a week before June 18 so you have time to troubleshoot any edge cases.
7Update amux session configs (if applicable)
If you manage Gemini CLI sessions through amux, update your session launch commands to use agy:
# Old amux session launch
tmux new-session -s gemini-agent -d 'gemini -p "work on feature branch"'
# New amux session launch
tmux new-session -s antigravity-agent -d 'agy -p "work on feature branch"'
See Running Antigravity CLI with amux below for more on managing Antigravity sessions alongside Claude Code.
Pricing Changes
The pricing model change is one of the most significant shifts in the transition. Gemini CLI was unusually generous for a production-grade AI tool: 1,000 requests per day at no cost with a standard Google account login (via OAuth), giving access to Gemini 2.5 Pro at zero marginal cost. This drew significant adoption from developers who found Claude Code's $20/month minimum too expensive for exploration.
Antigravity CLI requires a Google AI Pro or Ultra subscription:
| Plan | CLI Access | Models | Price |
|---|---|---|---|
| Individual free tier | ✘ Ends June 18 with Gemini CLI | — | $0 |
| Google AI Pro | ✔ Antigravity CLI included | Gemini 3.5 Flash / Pro | ~$20/mo |
| Google AI Ultra | ✔ Antigravity CLI included | Gemini 3.5 Pro (higher limits) | ~$100–200/mo |
| Gemini API (pay-as-you-go) | ✔ Via API key | Gemini 3.5 Flash / Pro | Per token (see ai.google.dev/pricing) |
| Enterprise (Vertex AI) | ✔ Separate timeline | All Gemini models | Enterprise contract |
Comparison: Gemini CLI vs Antigravity CLI vs Claude Code
With Gemini CLI ending and Antigravity CLI launching, many developers are re-evaluating their terminal coding agent. Here is how the three main options compare as of June 2026:
| Feature | Gemini CLI (ending Jun 18) |
Antigravity CLI (successor) |
Claude Code (Anthropic) |
|---|---|---|---|
| CLI command | gemini | agy | claude |
| Underlying model | Gemini 2.5 Pro | Gemini 3.5 Flash/Pro | Claude Opus 4.6 |
| Context window | 1M tokens | 1M tokens | 200K tokens |
| Free tier | 1,000 req/day | None (Pro required) | None (Pro required) |
| Starting price | $0 (ending) | ~$20/mo (Google AI Pro) | $20/mo (Claude Pro) |
| Open source | ✔ Apache 2.0 | ✘ Closed source | ✘ Closed source |
| Hooks | ✔ | ✔ | ✔ (CLAUDE.md + hooks) |
| Subagents | ✔ | ✔ | ✔ (Agent SDK) |
| Extensions/Plugins | ✔ Extensions | ✔ Plugins | ✔ MCP servers |
| SWE-bench Verified | ~80.6% (Gemini 3.1 Pro) | ~80.6%+ (Gemini 3.5) | ~80.8% |
| IDE integration | Gemini Code Assist | Antigravity IDE | Cursor, VS Code |
| Multi-session mgmt | Manual tmux | Manual tmux | amux, Claude Squad |
The practical coding performance between Antigravity CLI and Claude Code is close — Anthropic's Claude Opus 4.6 scores approximately 80.8% on SWE-bench Verified versus Gemini 3.1 Pro at approximately 80.6%, a gap well within noise. The differentiators are elsewhere: Antigravity's 1M context window gives it a structural advantage for large codebases; Claude Code's ecosystem (MCP servers, hooks, session managers, Agent SDK) gives it an orchestration edge.
Running Antigravity CLI with amux
amux is an open-source control plane for managing multiple AI coding agent sessions from a single web dashboard. It works with any terminal-based agent — including Antigravity CLI. If you run Antigravity sessions alongside Claude Code sessions, amux coordinates them through shared tmux windows.
gemini with agy in your amux session launch commands is all that is required.
To launch an Antigravity CLI session via amux:
# Install amux (if not already installed)
pip install amux
# Launch amux server
amux serve &
# Create a new Antigravity CLI session
# In the amux web dashboard or via REST API:
# POST /api/sessions { "name": "agy-worker-1", "command": "agy" }
# Or create via tmux directly (amux picks it up)
tmux new-session -s agy-worker-1 -d 'agy'
# Assign it a task via the amux kanban board
# and monitor output in the web dashboard at http://localhost:8822
With amux, you can run 5–20 Antigravity CLI agents in parallel, assign them tasks from a shared board, inspect their output without switching terminals, and set up a self-healing watchdog to restart crashed sessions automatically. See the getting started guide or GitHub repo for setup instructions.
Frequently Asked Questions
Orchestrate Antigravity CLI alongside Claude Code
amux is a free, open-source control plane for running multiple AI coding agent sessions in parallel — including Antigravity CLI. Web dashboard, self-healing watchdog, kanban board, mobile app.
Related Guides
- AI Coding Tools Compared: Antigravity vs Claude Code vs Cursor (2026)
- Best Claude Code Session Managers 2026 — 6 Tools Compared
- Best AI Model for Coding 2026: Benchmarks & Real-World Results
- AI Coding Agent Cost Guide 2026: Budgeting for Claude Code, Cursor & More
- Claude Code Hooks Cookbook: Automation Recipes