The Gemini CLI isn’t being updated. It’s being retired.
According to Google’s developer blog, Antigravity 2.0 replaces the Gemini CLI entirely, introducing a rebuilt command-line interface written in Go, a Python SDK installable via pip install google-antigravity, a desktop application, and native support for multi-agent orchestration. The prior Gemini CLI reportedly accumulated over 100,000 GitHub stars and 6,000 merged pull requests before the transition, figures that indicate genuine developer adoption, making the forced migration meaningful at scale. The replacement is reportedly free for developers and released under an Apache 2.0 license, though both claims require human validation against the live repository before treating them as confirmed.
The new slash command system, reportedly including /goal, /grill-me, /schedule, and /browser, signals a structural shift in how Google envisions developer interaction with its agentic tooling. /goal suggests persistent task framing across sessions. /grill-me implies interactive evaluation or testing workflows. /schedule and /browser point toward background execution and web-integrated agents respectively. These aren’t cosmetic additions. They represent a different mental model: the developer sets objectives and the agent executes across sessions, rather than the developer issuing one-off commands.
That shift has architecture implications that the announcement doesn’t address. Running parallel subagents and cron-scheduled background tasks against live APIs introduces questions about sandboxing boundaries, rate limit exposure, and what happens when a scheduled agent encounters an unexpected state. These aren’t hypothetical edge cases, they’re the first questions any team will face when moving beyond demo workflows. The announcement, as reported, doesn’t speak to them.
Antigravity 2.0 also arrives on the same day Google reportedly launched Gemini 3.5 Flash, the model layer underneath this execution layer. The pairing matters: Gemini 3.5 Flash is Google’s reportedly faster mid-tier model, and Antigravity 2.0 is the tooling designed to run agentic workflows on top of it. The two announcements together constitute a complete developer platform pitch, not just incremental product updates.
Agentic developer tooling is converging fast. Anthropic’s Claude Code, OpenAI’s deployment infrastructure, and now Google’s Antigravity 2.0 are all competing for the same target: the team building the first production-grade agentic system in their organization. The differentiating factor isn’t model capability alone, it’s which platform makes the transition from prototype to production the most friction-free.
What to Watch
Don’t expect the migration to be painless. Rebuilding in Go means a different binary, a different install path, and potentially different extension behavior for any team that’s customized Gemini CLI tooling. The Apache 2.0 license, if confirmed, is a meaningful signal for enterprise adoption, but tooling migrations at the CLI level consume engineering cycles regardless of licensing. Teams currently building on Gemini CLI should verify the official migration path at the Google Developers Blog before any production timelines are set.
The catch is that all technical specifications in this brief are reported claims pending primary source validation. The Google Developers Blog URL for the Antigravity transition is currently inaccessible. Treat slash command names, SDK install paths, and architecture specifics as subject to revision until the source is confirmed.