Is Google Gemini CLI Shutting Down? June 18 Deadline and Antigravity Migration Guide

核心结论

If you're searching "is Gemini CLI shutting down" or "Gemini CLI June 18 deadline," the short answer is: Yes, Google is retiring Gemini CLI and Gemini Code Assist IDE extensions for individual users, free-tier users, and Google AI Pro/Ultra subscribers on June 18, 2026. Enterprise and paid API customers are not affected. The official migration path is Antigravity CLI — a closed-source Go binary that shares the same agent harness as Antigravity 2.0. You have 4 days to migrate or switch to an alternative like Claude Code, Codex CLI, or Cursor.

Who's Affected (and Who Isn't)

On May 19, 2026 at Google I/O, Google announced that Gemini CLI and Gemini Code Assist IDE extensions will stop serving requests for specific user tiers starting June 18. This is not a full product shutdown — it's a tier-level sunset.

Losing access on June 18:

• Google AI Pro subscribers
• Google AI Ultra subscribers
• Free-tier Gemini Code Assist for individuals
• Individual Gemini Code Assist subscribers

Not affected:

• Enterprise organizations on Code Assist Standard or Enterprise licenses
• Teams with paid Gemini API keys or Agent Platform API keys
• Google Cloud customers with active licenses

If you're in the affected group, Gemini CLI will stop processing your requests entirely after June 18. The tool won't degrade gracefully — requests will simply fail.

What Antigravity CLI Actually Is

Antigravity CLI is the replacement. It's a closed-source binary written in Go — the command is agy — that shipped with Antigravity 2.0 at Google I/O 2026. The original Antigravity (November 2025) was a Cursor-like IDE with Gemini under the hood. Version 2.0 is a fundamentally different product: it centers the agent, not the editor.

The architectural difference matters. In Antigravity 2.0, the AI agent is the primary interface — the editor is just one of many tools the agent can invoke. This is the same pattern Claude Code and Codex CLI have been pursuing, where the agent plans, reasons, executes multi-step tasks, and uses external tools autonomously.

Critically, Antigravity CLI shares the same agent harness as the Antigravity 2.0 desktop app. Improvements to the core agent — reasoning upgrades, tool-use enhancements, model switches — automatically roll out to the CLI without separate updates. By default, it runs on Gemini 3.5 Flash, which outperforms Gemini 3.1 Pro across nearly all benchmarks while running 4x faster than other frontier models.

What You Lose in the Transition

The migration isn't frictionless. Several Gemini CLI features don't carry over cleanly:

1. settings.json configuration Gemini CLI's fine-grained context file management and model parameter tuning via settings.json doesn't map directly to Antigravity's configuration model. You'll need to rebuild context rules from scratch.

2. MCP integrations (silent failure trap) Antigravity CLI supports MCP servers, but the configuration format is different. If you copy your Gemini CLI MCP config directly, it will silently fail — no error message, just non-functional tool access. This is the most commonly reported migration pain point. You must manually convert to Antigravity's MCP configuration format.

3. IDE and CI pipeline integration Gemini CLI was designed for clean integration with existing IDEs and CI/CD pipelines. Antigravity CLI is more opinionated about working within the Antigravity ecosystem, though standalone terminal use is supported.

4. Open-source transparency Gemini CLI was open-source (TypeScript on GitHub with community contributions). Antigravity CLI is a closed-source Go binary. The Hacker News thread on this announcement generated hundreds of comments criticizing the bait-and-switch — developers invested in an open-source ecosystem only to have it replaced by a proprietary binary they can't inspect or fork.

What Antigravity CLI Improves

Despite the migration friction, there are genuine improvements:

• Shared agent harness: Core agent capabilities improve continuously without CLI-specific releases. Model upgrades, reasoning improvements, and new tool integrations appear automatically.
• Gemini 3.5 Flash default: Faster and more capable than the Gemini 3 models Gemini CLI used. Benchmarks show it outperforming Gemini 3.1 Pro across coding, reasoning, and multimodal tasks.
• Agent-first architecture: Rather than treating AI as smart autocomplete, Antigravity CLI treats it as an autonomous agent that plans, reasons, and executes — the same paradigm Claude Code and Codex CLI are built on.
• Backward compatibility bridge: Google provides automatic onboarding conversion for Gemini CLI settings, plus explicit agy migrate commands for manual migration.

Migration Steps (Before June 18)

If you need to migrate now:

1. Install: npm install -g @google/antigravity or download the agy binary from Google's site
2. Authenticate: agy auth login
3. Import plugins: agy migrate import-gemini-cli
4. ⚠️ Convert MCP config manually: This is the trap. The automatic import does not handle MCP configuration format conversion. You must rewrite your MCP server definitions in Antigravity's format. Test with agy mcp list after conversion.
5. Rebuild context rules: Gemini CLI's settings.json context definitions need to be recreated in Antigravity's configuration system.
6. Validate: Run agy check and do a test task to confirm everything works.

Google's official migration documentation: antigravity.google/docs/gcli-migration

Alternatives If You Don't Want Antigravity

If you'd rather not migrate to a closed-source Google product, you have several strong alternatives:

What This Means for Developers

Google's decision to sunset Gemini CLI for individuals reflects a broader industry reality: AI coding tools are converging on agent-first architectures. Claude Code, Codex CLI, Cursor Agent, and now Antigravity CLI all treat the AI as an autonomous agent rather than a completion engine.

The timing is aggressive — a 30-day migration window with a hard cutoff — and the closed-source shift has drawn justified criticism. But the technical direction is consistent with where the market is going. Developers who embraced Gemini CLI for its open-source flexibility and IDE integration now face a choice: follow Google into the Antigravity ecosystem, switch to an open-source alternative like Codex CLI or Continue.dev, or pay for an enterprise license to keep Gemini CLI access.

The deadline is June 18, 2026 — 4 days from now. If you're affected, don't wait until the last day. MCP configuration conversion alone can take several hours to debug, and you want buffer time to validate your new setup before the old one stops working.