Google Transitions Gemini CLI to New Antigravity Platform

Google is transitioning Gemini CLI to the new Antigravity CLI to better support complex, multi-agent developer workflows. Consumer and free users have until June 18, 2026, to migrate before the legacy Gemini CLI services are discontinued. The new Go-based tool offers improved performance and background task orchestration while maintaining core features from the original CLI.

Key Points

• Google is consolidating Gemini CLI into the Antigravity 2.0 platform to support multi-agent orchestration.
• Antigravity CLI offers performance upgrades, including Go-based execution and asynchronous background tasking.
• Consumer and free-tier users must migrate to Antigravity CLI before Gemini CLI services end on June 18, 2026.
• Enterprise customers with Gemini Code Assist Standard or Enterprise licenses will continue to receive support for Gemini CLI.
• The new platform maintains feature parity for critical tools like Agent Skills, Hooks, and Subagents via a new plugin system.

Sentiment

The overall sentiment is negative toward the article’s migration story. Hacker News largely disagrees with the implication that this is a straightforward modernization, instead framing it as confusing product churn that undermines confidence in Google’s developer tooling. A minority accepts the platform rationale, but even that support is tempered by concerns about rollout quality and brand clarity.

In Agreement

• Antigravity can be understood as a broader agent platform while Gemini is more naturally a model brand, so a separate platform name may make sense.
• A unified platform could simplify billing, quotas, integrations, and support for models beyond Gemini.
• Gemini CLI had quality, performance, and maintenance problems, so replacing it with a more focused agent harness could be a practical improvement.
• The economics of free or heavily subsidized AI coding tools may make standalone CLI products difficult to sustain without a tighter platform model.

Opposed

• The move reinforces the perception that Google repeatedly kills or renames developer products before users can safely depend on them.
• Antigravity branding is confusing because many developers associate it with an IDE, not a CLI or agent platform.
• Google could have preserved the Gemini CLI name, provided aliasing, or maintained compatibility while changing the underlying architecture.
• Users report that Antigravity CLI does not yet feel migration-ready, with rough edges around extensions, integrations, themes, quotas, and configuration awareness.
• The transition makes some developers less willing to adopt Google LLM tooling or other Google developer products.