By Google deprecated Gemini CLI on May 19 — and set a hard shutdown for June 18. If you’re one of the hundreds of thousands of developers who built Gemini CLI into your workflow, you have less than four weeks to migrate to Antigravity CLI or lose access entirely. The migration isn’t hard, but the new tool has real issues worth knowing before you commit.
What Google Shut Down — and Why
At Google I/O 2026, Google announced Antigravity 2.0 and simultaneously deprecated three products: Gemini CLI, Code Assist IDE, and its legacy agent tooling. All three are now unified under the Antigravity brand. The June 18 deadline applies to individual accounts on free, Pro, and Ultra plans. Enterprise users on Code Assist Standard or Enterprise licenses are unaffected.
The replacement ships five surfaces: a standalone desktop app for multi-agent orchestration, a CLI tool (invoked as agy), an SDK for custom agents, a Managed Agents tier inside the Gemini API, and an enterprise deployment path. That’s an ambitious consolidation. Whether it’s an upgrade depends on what you were using before.
How to Migrate in Five Commands
The migration is non-destructive. Your old ~/.gemini/ config stays intact until June 18, so rollback is available if something breaks.
# Install the Antigravity CLI
curl -fsSL https://antigravity.google/cli/install.sh | bash
# Authenticate
agy auth login
# Import your Gemini config and plugins
agy plugin import gemini
# Move workspace skills
mv .gemini/skills/ .agents/skills/
# Validate the environment
agy doctorThe binary is agy, not antigravity or gemini. On Unix it drops into ~/.local/bin/; on Windows it goes to %LOCALAPPDATA%\Antigravity\. After agy doctor passes clean, you’re done. Most developers report the full process takes under ten minutes. For the full command mapping from Gemini CLI to Antigravity CLI, Agentpedia’s migration guide is the most complete reference available.
The Part Google Isn’t Advertising
The new tool has a quota tracking problem that’s biting developers. The /usage command only updates after you quit and relaunch agy — you can’t monitor consumption in real time during long agent runs. Google has acknowledged this as a known issue but hasn’t given a fix date. Developers have reported running out of quota mid-session with no warning.
The billing model also changed. It’s now compute-based rather than daily prompt limits, with quota refreshing every five hours instead of daily. Google hasn’t published a compute-unit conversion table, so there’s no reliable way to estimate what a given agent run will cost before it starts. Community workarounds exist: the open-source antigravity-usage CLI tracks quota between sessions, and an unofficial antigravity-panel extension provides monitoring inside the IDE.
The Open-Source Controversy
Gemini CLI had over 100,000 GitHub stars and more than 6,000 merged pull requests from the developer community. Antigravity CLI, its replacement, is closed-source for non-enterprise users. The Register called it a bait-and-switch. FOSS Force described it as Google “harvesting OSS community labor, then closing the gate at the enterprise boundary.” The Hacker News thread on the deprecation ran thousands of comments, most negative.
The frustration is straightforward: developers invested engineering time in a tool Google positioned as a community project, and the replacement doesn’t extend those terms. Google says it plans to support open APIs and plugin ecosystems — but that’s a future promise, not a current feature.
Is It Worth Switching From Cursor or Claude Code?
If you’re already on Cursor 3 or Claude Code 1.3 and happy there, Antigravity 2.0 isn’t a reason to switch today. The honest comparison as of May 2026:
- Antigravity 2.0 leads on parallel multi-agent workflows and rapid prototyping. Gemini 3.5 Flash runs at around 289 tokens per second — about four times faster than GPT-5.5 or Opus 4.7. Best fit for Google-stack projects or teams that need browser automation baked in.
- Cursor 3 remains the best daily driver for most developers. Stable, familiar, well-integrated into VS Code workflows.
- Claude Code 1.3 leads on complex reasoning and production-safety tasks. The model’s conservatism is an asset when the cost of a wrong decision is high.
Expert consensus: switching has real cost, and the marginal benefit is small if you’re already shipping. The case for Antigravity is strongest if you’re on Gemini CLI (you have to move anyway) or if you specifically need parallel agent execution.
Pricing
Google restructured its AI subscription tiers alongside the Antigravity 2.0 launch:
| Plan | Price | Antigravity Usage |
|---|---|---|
| Pro | $20/month | Base quota |
| AI Ultra | $100/month | 5x Pro |
| AI Ultra Premium | $200/month | 20x Pro |
The $100/month AI Ultra tier is new — Google dropped the power-user entry price from $250 to $100. The Premium tier now costs $200 (down from $250) and delivers 20x the base quota.
Bottom Line
If you’re on Gemini CLI, migrate now. The process is fast, the rollback path exists until June 18, and waiting doesn’t make it easier. Run agy doctor after setup and verify your workspace skills loaded correctly. Install the community quota tracker to compensate for the /usage bug if you run long sessions.
If you’re on Cursor or Claude Code and shipping well, Antigravity 2.0 is worth watching — not switching to today. The parallel agent capability is genuinely ahead. When Google resolves the quota visibility problem and publishes compute pricing, the evaluation gets more interesting.
