Google is sunsetting Gemini CLI on June 18, 2026, replacing it with Antigravity CLI, a Go-based agent-first tool with async workflows and a unified backend.
Key Takeaways
Hard deadline June 18, 2026: Gemini CLI and Gemini Code Assist IDE extensions stop serving requests for all free, Pro, and Ultra users.
Enterprise carve-out: Orgs on Code Assist Standard/Enterprise or Google Cloud licenses keep access; Gemini CLI remains available via paid API keys.
Antigravity CLI differences: Go-based for speed, async multi-agent orchestration, shared harness with Antigravity 2.0 desktop app, and plugins replacing Extensions.
Not 1:1 parity at launch: Agent Skills, Hooks, Subagents, and Extensions (as plugins) carry over, but Google acknowledges gaps and invites feature requests.
Open source status lost: Gemini CLI was Apache 2 licensed with 100k GitHub stars; Antigravity CLI repo currently has only a README and a demo gif.
Hacker News Comment Review
The open-source regression is the sharpest technical objection: Gemini CLI was Apache 2 with active community contributions; Antigravity CLI ships closed-source with no repo substance yet.
Commenters flag a geo-eligibility wall blocking signup for Antigravity in some countries, making the forced migration immediately broken for affected users.
Programmatic usage and Agent Client Protocol support are unaddressed in Antigravity docs, a gap that matters for anyone embedding the CLI in pipelines.
Notable Comments
@simonw: Confirms Antigravity CLI repo has only a README and gif vs. Gemini CLI’s full Apache 2 open-source history.
@2001zhaozhao: No mention of programmatic usage or Agent Client Protocol support anywhere in Antigravity docs.