Google Just Killed Gemini CLI — Antigravity 2.0 Is the New Terminal King

Google didn’t just update Gemini CLI. They killed it.

On June 18, 2026, Gemini CLI stopped serving requests for anyone on the free tier, Google AI Pro, or Google AI Ultra. If you were one of the millions who built workflows around it — over 100,000 GitHub stars, 6,000 merged PRs — your terminal agent effectively went dark unless you pay for enterprise Gemini Code Assist.

The replacement? Google Antigravity 2.0 — a complete rebuild with a new desktop app, a Go-built CLI, a unified agent harness, and multi-agent orchestration baked in from day one.

This isn’t a v1.1. It’s a platform pivot. And it changes how Google fits into the terminal AI war against Claude Code, Codex CLI, and the open-source alternatives.

What Actually Happened

May 19, 2026 — Google I/O. The Antigravity team announced:

• Antigravity 2.0 — standalone desktop app (macOS, Linux, Windows)
• Antigravity CLI — new terminal interface, built in Go
• Antigravity SDK — for building your own agent surfaces
• Managed Agents API — cloud-deployed agents

June 18, 2026 — Hard cutoff. Gemini CLI + Gemini Code Assist IDE extensions stop serving free/Pro/Ultra users. Enterprise customers on Standard/Enterprise licenses keep access.

Now — Migration window is closed. You’re either on Antigravity or you’re shopping for a new terminal agent.

Why Google Did This

The official line: “your workflows have simply outgrown those early days of 2025.”

Translation: Single-agent chat in a terminal doesn’t cut it anymore.

Claude Code proved developers want agents that act — run commands, edit files, spawn subagents, coordinate. Codex CLI doubled down. The open-source ecosystem (Aider, OpenCode, Kilo, opencode) moved even faster.

Gemini CLI was built for a world where “agent” meant “chat with tool access.” That world is gone.

Google’s answer: unify everything on one agent harness. The CLI, the desktop app, the enterprise platform, the cloud API — all share the same brain. Improve the harness once, every surface gets better.

Antigravity CLI: What You Actually Get

Built in Go — Finally Fast

Gemini CLI was TypeScript. Antigravity CLI is Go. The difference is visible immediately:

• Cold start: ~200ms vs ~2s
• Memory footprint: ~40MB vs ~150MB
• No Node runtime dependency — single binary

For terminal diehards, this matters. You feel it in every keystroke.

Multi-Agent Orchestration, Not Chat

The old model: you ask, agent answers, you ask again.

Antigravity model: you define a goal, agents coordinate.

# In Antigravity CLI
/goal "Refactor the auth module to use JWT, add tests, update docs"

The main agent spawns subagents:

• One reads the codebase, maps dependencies
• One writes the JWT implementation
• One generates test coverage
• One updates documentation
• Main agent reviews, merges, runs CI

All async. Your terminal isn’t blocked. You can /schedule it to run tonight while you sleep.

Slash Commands That Actually Change Workflows

The /grill-me pattern alone prevents hours of wasted context. The agent forces alignment before burning tokens.

Scheduled Tasks = Agents That Work While You Don’t

/schedule daily 02:00 "Review dependabot PRs, run tests, auto-merge green"
/schedule weekly monday 09:00 "Generate weekly changelog from merged PRs"

This is the feature that makes Antigravity feel like a platform instead of a tool. You’re not babysitting the agent. You’re managing a fleet.

Migration: What Carries Over, What Doesn’t

✅ Carries Over (Mostly)

• Agent Skills → Now Antigravity Plugins (JSON format, same concept)
• Hooks → JSON hooks, more powerful, version-controlled
• MCP Servers — Full compatibility, same config format
• Subagents — Now “dynamic subagents” with better isolation
• Extensions → Plugins, same capability surface

❌ Breaking Changes

• Config file location — ~/.gemini → ~/.antigravity
• Settings schema — New unified schema across CLI + desktop
• Conversation history — Not auto-migrated. Export/import via @conversation dropdown in desktop app
• IDE extensions — Gemini Code Assist extensions deprecated. New Antigravity IDE extensions coming (VS Code, JetBrains, Antigravity IDE)

Migration Path (Do This Now)

# 1. Install Antigravity CLI
curl -fsSL https://antigravity.google/download/cli | sh

# 2. Run migration wizard (imports skills, MCP, hooks)
antigravity migrate --from-gemini-cli

# 3. Verify
antigravity doctor

# 4. Test a real task
antigravity run "/goal 'Add README to this repo'"

The wizard handles ~80% of configs automatically. The rest you’ll tweak manually — mostly hook syntax changes.

Antigravity 2.0 Desktop: Why It Exists

The CLI is for operators. The desktop app is for orchestrators.

Key differences:

• Visual artifact review — See diffs, test output, browser screenshots in a review flow
• Project-based (not repo-based) — One project = multiple folders, custom permissions per folder
• Voice input with live transcription — Talk to agents, see text appear in real-time
• Standalone conversations — Detach a thread, hand it to a colleague, pick up later
• Scheduled Tasks UI — Visual cron builder, run history, notifications

Google’s internal teams “dual-wield” — Antigravity 2.0 for planning/review, CLI for execution, IDE of choice for editing. That’s the intended workflow.

How It Stacks Up (August 2026)

*BYOH = Bring Your Own Harness

The verdict: Antigravity CLI is the best pure terminal experience if you’re all-in on Google’s ecosystem. Unified harness across surfaces is a genuine differentiator — fix a hook once, works everywhere.

But — model lock-in is real. You get Gemini. Want Opus 5? GPT-5.6? Qwen3-Max? You’re not getting them natively in Antigravity. The open-source CLIs (OpenCode, Kilo, Aider, opencode) win on model freedom.

The Strategic Picture: Google’s Platform Play

This isn’t really about a CLI. It’s about owning the agent layer.

1. Harness co-optimized with Gemini training — Google controls model + harness + eval. Faster iteration than anyone.
2. Managed Agents API — Deploy agents to Google Cloud, call via API. No local compute needed.
3. Antigravity SDK — Build your own agent surfaces (internal tools, customer-facing, whatever) on Google’s harness.
4. Enterprise lock-in — Standard/Enterprise customers stay on Gemini CLI for now, but migration path points to Antigravity Enterprise Platform.

Google is building the AWS for AI agents. The CLI is just the developer on-ramp.

Should You Switch?

Stay with Antigravity if:

• You’re already in Google Cloud / Gemini ecosystem
• You want the fastest, lightest terminal agent (Go binary wins)
• Multi-agent async workflows match how you work
• You want a path to cloud-deployed agents without rewriting

Look elsewhere if:

• You need model choice (Opus 5, GPT-5.6, local models)
• You’re invested in Claude Code / Codex workflows that already work
• You refuse vendor lock-in on principle
• Your team uses mixed IDEs and you need universal IDE extensions (coming, not here)

The pragmatic middle:

Run Antigravity CLI alongside an open-source CLI. Use Antigravity for Google-integrated work (Cloud, Firebase, Workspace APIs). Use OpenCode/Kilo/Aider for everything else. They’re all just terminals — run both.

What’s Next

Google’s roadmap (from I/O + blog posts):

• Remote control — Control desktop agents from CLI, vice versa
• Cloud-deployed agents — Managed Agents API GA
• IDE extensions — VS Code, JetBrains, Antigravity IDE plugins
• More model tiers — Gemini 3.5 Ultra, future Flash/Pro updates
• Agent marketplace — Share/install pre-built agent configurations

The platform is early. But the foundation — unified harness, Go CLI, async multi-agent — is solid.

TL;DR

• Gemini CLI is dead for free/Pro/Ultra users since June 18, 2026
• Antigravity CLI replaces it — Go binary, multi-agent, async, scheduled tasks
• Antigravity 2.0 desktop adds visual review, project-based workspaces, voice
• Unified harness across CLI, desktop, cloud, SDK = Google’s moat
• Model lock-in to Gemini is the trade-off
• Migration is straightforward for skills/MCP/hooks; conversation history needs manual export

The terminal AI war just got a new front. Google isn’t playing catch-up anymore — they’re building the platform they should’ve built in 2025.

Related articles

• Claude Code Alternatives in 2026: 12 Options Compared
• Context Engineering for Coding Agents: How to Make Every Token Count
• Your AI Agents Config Directory Is Now the Most Dangerous Place on Your Machine

Migrated from Gemini CLI? Hit me up on X @terminalblog_en — collecting real migration stories for a follow-up.