Summary: Free and Google AI Pro/Ultra access to Gemini CLI ended on June 18, 2026, and Google now points those users to Antigravity CLI (the agy command). This guide walks through installing it, signing in, importing your old Gemini CLI extensions and skills, and fixing the setup errors people hit most often. Every step below was checked against Google's official Antigravity docs on October 31, 2026.
What changed, and who has to move
Google announced the switch on the Google Developers Blog on May 19, 2026. Starting June 18, 2026, Gemini CLI and the Gemini Code Assist IDE extensions stopped serving requests for people using them free of charge (Gemini Code Assist for individuals) and for Google AI Pro and Ultra subscribers. The Gemini CLI GitHub README now says the tool is meant for organizations with Gemini Code Assist Standard or Enterprise licenses, Code Assist for GitHub on Google Cloud, and legacy paid API or Vertex keys.
So the practical rule is simple:
- You used Gemini CLI with a personal Google account (free, Pro or Ultra): move to Antigravity CLI.
- Your company pays for Gemini Code Assist Standard/Enterprise: Gemini CLI keeps working for you, though you can also try Antigravity CLI with your Google Cloud projects.
Google says there is no 1:1 feature parity yet, but Antigravity CLI keeps Agent Skills, Hooks, Subagents and Extensions (now called plugins). It is written in Go and shares the same agent harness as the Antigravity desktop app, so improvements to the core agent show up in both.
Step 1: Install Antigravity CLI
The official Quickstart lists one installer command per operating system. At the time of writing, the download page shows Antigravity CLI version 1.4.10.
macOS, Linux or Googlebook
curl -fsSL https://antigravity.google/cli/install.sh | bash
The binary lands in ~/.local/bin/agy.
Windows
In PowerShell:
irm https://antigravity.google/cli/install.ps1 | iex
In Command Prompt (CMD):
curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd
On Windows the default location is C:\Users\<username>\AppData\Local\agy\bin.
Check that it worked
Open a new terminal window and run:
agy --version
If you get agy: command not found, jump to the troubleshooting section below. It is almost always a PATH problem.
Step 2: First launch and sign-in
Go to a project folder and start the terminal UI:
cd your-project
agy
On the first launch, the CLI walks you through three quick choices:
- Color scheme: Dark, Solarized Dark, Solarized Light, or your terminal's default.
- Rendering mode: Alt-Screen (a full-screen buffer) or Inline (output stays in your normal terminal history). Choose Inline if you like scrolling back through earlier output.
- Workspace trust: confirm that you trust the folder before the agent starts indexing files.
Sign-in works in one of three ways, according to the Authenticate guide:
- Local machine: the CLI first checks your operating system's keyring (Apple Keychain, Linux Secret Service over D-Bus, or Windows Credential Manager). If no saved session is found, it opens your default browser so you can sign in with your personal Google account.
- Over SSH: the CLI notices it can't open a browser and prints an authorization URL. Open that URL on your local computer, sign in, copy the code the browser shows, and paste it back into the remote terminal.
- Gemini API key (good for CI): set
"modelProvider": "gemini"in~/.gemini/antigravity-cli/settings.json, thenexport GEMINI_API_KEY="your-api-key". Setting only the environment variable does nothing. The CLI reads the key only fromGEMINI_API_KEY, not fromGOOGLE_API_KEYor a.envfile.
Signing in once is shared across the Antigravity app, IDE extensions and CLI on the same machine. To sign out and clear the saved keyring profile, type /logout in the prompt box.
Step 3: Bring over your Gemini CLI setup
If your machine still has Gemini CLI settings, the first agy launch detects them and shows a checklist. You pick which extensions and global settings to convert, and your session tokens move into the OS keyring. If you skipped that screen, or you want to redo it, follow these steps.
3a. Convert extensions to plugins
agy plugin import gemini
This reads your old extension manifests and converts them. The sample output in the docs shows old custom commands being turned into skills, and MCP server definitions being moved into mcp_config.json. Read the report it prints. Lines marked "skipped" simply mean nothing of that type was found.
3b. Keep your GEMINI.md and AGENTS.md
You don't have to change anything here. Antigravity CLI still reads GEMINI.md and AGENTS.md in your project folder, plus your global ~/.gemini/GEMINI.md.
3c. Move workspace skills (manual step)
This is the step people miss. Project-level skills used to live in .gemini/skills/. Antigravity CLI looks in .agents/skills/ instead:
mkdir -p .agents
git mv .gemini/skills .agents/skills # or plain mv if the folder isn't tracked
Global skills in ~/.gemini/skills/ still work, and ~/.gemini/antigravity-cli/skills/ is also accepted.
3d. Move MCP servers to their own file
Gemini CLI kept MCP servers inside ~/.gemini/settings.json. Antigravity CLI uses a separate file: ~/.gemini/config/mcp_config.json for global servers and .agents/mcp_config.json for one project. For remote SSE or WebSocket servers, rename the old url or httpUrl key to serverUrl:
{
"mcpServers": {
"my-remote-server": {
"serverUrl": "https://example.com/sse"
}
}
}
Step 4: Run your first task safely
The Quickstart uses a small demo you can copy:
- Run
mkdir agy-demo && cd agy-demo, thenagy. - Type a prompt such as Write a simple python script to fetch web page text and press Enter. The agent indexes the folder, makes a plan and proposes changes.
- Press Ctrl+R when prompted to open Artifact Review. Look over the diff, press Y to approve the new file, then Esc to go back.
- Ask it to Run the python script and show me the output, and press Y to allow the command.
- Exit with Ctrl+D or
/exit.
Pay attention to the execution mode while you work. Press Shift+Tab to cycle through modes:
- default asks before editing files and before running commands.
- accept-edits approves file edits automatically but still asks before running commands.
- auto (Preview) runs commands in a sandbox and still asks before anything irreversible. It needs v1.3.5+ on macOS/Linux or v1.4.4+ on Windows.
- plan lays out the steps before writing any code.
Stay in default mode until you trust how the agent behaves in a given repo.
A few commands are worth learning on day one: /usage (credit use and quota), /config (settings), /permissions, /rewind or /undo, /resume, and ? for the full command list. To run commands from scripts, headless mode runs one prompt and exits: agy -p "your prompt", with --output-format json for output a program can parse. Authenticate once in an interactive session first. Otherwise a CI run exits with an "authentication required" error.
Plans and limits compared
Antigravity's pricing page and Plans doc describe limits in terms of quota rather than fixed prompt counts. The table below sticks to what those official pages say. Google AI Pro and Ultra prices aren't listed on the Antigravity pricing page, so check your Google One plan for those.
| Plan | Price shown | Quota (per Plans doc) | Extra usage |
|---|---|---|---|
| Individual (no subscription) | $0/month | A "meaningful quota" refreshed weekly, with a weekly rate limit; unlimited Tab completions | AI credit overages described for Pro/Ultra only |
| Google AI Pro | Not listed on Antigravity page | High quota refreshed every five hours until a weekly limit is reached | Purchased AI credits for overage |
| Google AI Ultra | Not listed on Antigravity page | Highest quota refreshed every five hours, highest weekly limit, third-party models | Purchased AI credits for overage |
| Business (Google Cloud / Gemini Enterprise) | API: consumption-based; Standard/Plus from $30 per seat per month; pay-as-you-go with $0 seat fee | Under Google Cloud terms, with spend caps and admin controls | Consumption pricing |
The Plans doc also says bring-your-own-key for extra rate limits isn't supported. The Gemini API key option in Step 2 sends requests straight to the Gemini API, which bills separately, so it doesn't add to your plan quota.
Editor's note
Good fit: developers who used Gemini CLI on a personal account and want to stay in the terminal, and anyone who wants background subagents without opening a full IDE.
Not ideal: teams that depend on custom Gemini CLI themes or experimental visual overlays (the migration doc warns these may not carry over), or anyone who needs fixed, predictable prompt counts. Quota depends on how much work each task takes.
Common errors and fixes (from the official troubleshooting page):
agy: command not found: addexport PATH="$HOME/.local/bin:$PATH"to~/.bashrcor~/.zshrc, then reload it. On Windows, add the install folder to your user Path and restart the terminal.secret keyring is lockedon Linux over SSH: make sure GNOME Keyring or KWallet is unlocked. In headless sessions, start a D-Bus session withexport $(dbus-launch).update.lockwarning or the CLI hangs while updating: delete~/.gemini/antigravity-cli/updater/update.lock, or setAGY_CLI_DISABLE_AUTO_UPDATE=true.- API key mode exits at startup:
modelProvideris set togeminibutGEMINI_API_KEYisn't exported in that shell. - Skills don't show up as slash commands: they're still in
.gemini/skills/. Move them to.agents/skills/.
FAQ
Can I still use Gemini CLI for free?
No. Since June 18, 2026, Gemini CLI no longer serves free individual use or Google AI Pro/Ultra accounts. It stays available for Gemini Code Assist Standard/Enterprise organizations and paid API keys. Free personal use has moved to Antigravity CLI's $0 Individual plan.
Do I need to rewrite my GEMINI.md files?
No. Antigravity CLI reads the same project GEMINI.md and AGENTS.md files and your global ~/.gemini/GEMINI.md. What you do need to move are workspace skills (to .agents/skills/) and MCP server entries (to mcp_config.json).
How do I see how much quota I have left?
Run /usage inside the CLI. If you're on a paid plan with AI credits, the right side of the status line shows your remaining credit count. The useG1Credits setting (or "Use G1 Credits" in /config) controls whether credits are spent once your plan quota runs out.
Related on this blog: Cline Tutorial: Plan, Act and Roll Back Safely in VS Code · Aider Not Working? Fixes for Edit, Token and API Key Errors · Windsurf Is Now Devin Desktop: Fixes for Common Problems
If you only do one thing today, run agy plugin import gemini and move your .gemini/skills folder. That covers most of the migration.
Image credits: Google Developers Blog (official announcement cover) and the author's own screenshots of public Google Antigravity pages (Quickstart, Gemini CLI migration guide, pricing). See the official screenshots at the end of this post.
Last verified: 2026-10-31 · By zeromy
Sources:
Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI
Gemini CLI GitHub README
Antigravity Quickstart
Antigravity Authenticate guide
Migrating from Gemini CLI
CLI troubleshooting
Execution modes
Plans · Pricing · Download
댓글
댓글 쓰기