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.

⚠️
Deadline: June 18, 2026. Gemini CLI (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.
TL;DR: Replace 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:

Enterprise timeline is different. Enterprise Gemini Code Assist customers (Standard and Enterprise tiers) have a separate, longer migration window. If your organization uses Gemini CLI through Vertex AI or enterprise contracts, contact your Google account team for your specific deadline.

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

DimensionGemini CLI (old)Antigravity CLI (new)
CLI commandgeminiagy
ExtensionsExtensions (~/.gemini/extensions/)Plugins (renamed, new path)
Open source✔ Apache 2.0 (GitHub)✘ Closed source
Free tier1,000 req/day (Google account)Requires Google AI Pro/Ultra plan
Underlying modelGemini 2.5 Pro / FlashGemini 3.5 Flash / Pro
IDE integrationGemini Code Assist (VS Code extension)Antigravity IDE (VS Code fork)
Config directory~/.gemini/~/.antigravity/ (verify against docs)
Custom commands~/.gemini/commands/*.tomlUpdated format (see docs)
The most disruptive change for most developers is the CLI command rename from 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:

FeatureStatus 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:

PlanCLI AccessModelsPrice
Individual free tier✘ Ends June 18 with Gemini CLI$0
Google AI Pro✔ Antigravity CLI includedGemini 3.5 Flash / Pro~$20/mo
Google AI Ultra✔ Antigravity CLI includedGemini 3.5 Pro (higher limits)~$100–200/mo
Gemini API (pay-as-you-go)✔ Via API keyGemini 3.5 Flash / ProPer token (see ai.google.dev/pricing)
Enterprise (Vertex AI)✔ Separate timelineAll Gemini modelsEnterprise contract
Developers who relied on Gemini CLI's free tier face the biggest disruption. A Google AI Pro subscription ($20/month) brings pricing in line with Claude Code Pro ($20/month). Developers evaluating both should read the AI Coding Tools Comparison for a full cost analysis.

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 commandgeminiagyclaude
Underlying modelGemini 2.5 ProGemini 3.5 Flash/ProClaude Opus 4.6
Context window1M tokens1M tokens200K tokens
Free tier1,000 req/dayNone (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✔ PluginsMCP servers
SWE-bench Verified~80.6% (Gemini 3.1 Pro)~80.6%+ (Gemini 3.5)~80.8%
IDE integrationGemini Code AssistAntigravity IDECursor, VS Code
Multi-session mgmtManual tmuxManual tmuxamux, 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.

amux is agent-agnostic. The web dashboard, kanban board, REST API, self-healing watchdog, and inter-session messaging all work with any process running in a tmux session. Replacing 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

What is replacing Gemini CLI?+
Google is replacing Gemini CLI with Antigravity CLI — the terminal component of the Google Antigravity 2.0 platform. The CLI command changes from gemini to agy. Antigravity CLI has been available to all users since May 19, 2026, and Gemini CLI stops serving requests on June 18, 2026 for Google AI Pro, Ultra, and free-tier users.
When exactly does Gemini CLI stop working?+
June 18, 2026 for Google AI Pro/Ultra and individual free-tier users. Enterprise Gemini Code Assist customers have a separate, longer migration window. The official Google announcement was made on May 19, 2026.
Is Antigravity CLI open source like Gemini CLI was?+
No. Gemini CLI was available under the Apache 2.0 license on GitHub, making it fully forkable and self-hostable. Antigravity CLI is a closed-source product tied to Google AI subscriptions. This is a significant shift that affects developers who value open-source tooling or who ran Gemini CLI on private infrastructure without sending traffic to Google's API.
What happens to the free tier (1,000 req/day)?+
The Gemini CLI free tier (1,000 requests/day with a Google account via OAuth) ends on June 18, 2026. Antigravity CLI requires a Google AI Pro subscription (approximately $20/month). There is no equivalent free tier in Antigravity CLI. Developers who used Gemini CLI specifically for its free access will need to pay for a subscription or evaluate alternatives like Aider (fully open source, bring your own API key) or Codex CLI.
Do my Gemini CLI Hooks still work in Antigravity CLI?+
Yes. Google confirmed that Hooks are fully retained in Antigravity CLI. Agent Skills and Subagents are also retained. Extensions are renamed to Plugins and the configuration path may differ — check the Antigravity CLI plugins documentation to verify your extension format is compatible.
Should I switch to Claude Code instead of Antigravity CLI?+
It depends on your priorities. Antigravity CLI retains the 1M token context window, which matters for large monorepos or long-running sessions. Claude Code has a richer orchestration ecosystem — MCP servers, hooks, the Agent SDK, and multi-session tools like amux and Claude Squad. SWE-bench scores are near parity (~80.8% vs ~80.6%). Both cost around $20/month at the entry tier. If the Antigravity migration is smooth, many developers will stay; if the free tier loss or closed-source shift is a dealbreaker, now is a natural switching point. See the full AI Coding Tools Comparison for more.
What is the new Antigravity CLI command?+
The new command is agy — replacing gemini. This is the core breaking change in the migration. Update all shell scripts, aliases, CI/CD configurations, and automation that calls gemini to call agy instead. Most workflows are otherwise compatible.

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.

View on GitHub Getting Started Guide

Related Guides