Gemini CLI: Transition to Antigravity CLI — Sunset Announced for June 18, 2026

Gemini CLI Transitions to Antigravity CLI: What Developers Need to Know

At Google I/O 2026, Google made a sweeping announcement that will affect every developer currently running Gemini CLI: the terminal agent is being succeeded by Antigravity CLI, a rewritten Go-based tool that forms the command-line surface of Google's new Antigravity 2.0 agentic development platform. The transition comes with a hard deadline — June 18, 2026 — after which Gemini CLI will stop serving requests for the majority of its user base.

Why Google Is Making the Change

Google framed the transition as a response to how developer workflows have evolved. When Gemini CLI launched, the goal was to prove that the terminal could be a first-class interface for agentic AI tasks. That experiment succeeded, but according to Google, the next frontier is multi-agent coordination — systems where multiple specialized agents communicate, split up work, and share a unified backend to solve complex problems.

Antigravity CLI is designed to serve that use case from the ground up. Built in Go rather than the TypeScript/Node.js stack underpinning Gemini CLI, it promises snappier execution and asynchronous workflow orchestration, allowing developers to run large-scale refactors or parallel research tasks in the background without locking up the terminal. The new CLI shares a unified server-side harness with the Antigravity 2.0 desktop application, meaning configurations and agent logic can be shared across surfaces.

What Changes on June 18, 2026

The June 18 date marks when Gemini CLI will stop responding to requests for the following groups:

• Google AI Pro and Ultra subscribers — must switch to Antigravity CLI
• Free-tier users (Gemini Code Assist for individuals) — must switch to Antigravity CLI
• Gemini Code Assist IDE extension users — affected for GitHub integrations and individual plans; no new GitHub installations will be accepted starting June 18

Who is NOT affected:

• Organizations with Gemini Code Assist Standard or Enterprise licenses retain full Gemini CLI access, including continued model updates and security fixes
• Developers using paid Gemini API or Gemini Enterprise Agent Platform API keys retain access
• Google Cloud project users can adopt Antigravity CLI immediately while maintaining existing infrastructure

What Carries Over to Antigravity CLI

Google confirmed that the most-used capabilities of Gemini CLI are preserved in the new platform:

• Agent Skills — reusable AI workflow automations
• Hooks — event-driven lifecycle triggers
• Subagents — parallel task delegation
• Extensions — now called Antigravity plugins, with the same underlying model

However, Google explicitly acknowledged that 1:1 feature parity will not be available at launch. Developers relying on niche CLI flags, specific configuration formats, or custom integrations may encounter gaps during the initial migration window.

The Open-Source Question

The Gemini CLI GitHub repository — which has accumulated over 100,000 stars and hundreds of community contributions — will remain publicly available as an Apache 2.0 licensed project. Google committed to continuing active development on the repository, including security fixes, bug patches, and model updates, specifically to serve enterprise customers on paid plans.

However, Antigravity CLI itself launched as a closed-source product, which became the flashpoint for community criticism. Within hours of the announcement, developers posted on GitHub Discussion #27274 — which attracted 74 comments within 24 hours — accusing Google of leveraging open-source community contributions to build a proprietary successor, effectively asking volunteers whether their work would flow primarily to enterprise customers.

Developer Reaction

The response across the developer community has been sharply negative across three themes:

1. Closed-source concerns — the lack of transparency around Antigravity CLI's internals, especially compared to the fully open Gemini CLI codebase
2. Usage quota frustrations — multiple developers reported hitting weekly limits after only a handful of requests on the new platform, a stark contrast to Gemini CLI's more permissive free tier
3. Trust erosion — recurring criticism of Google's history of deprecating tools developers rely on, drawing unfavorable comparisons to previous Google product shutdowns

Gemini CLI Lead Product Manager Dmitry Lyalin posted directly in the GitHub discussion to address community questions and committed to video walkthroughs and migration documentation in the coming weeks.

What Developers Should Do Now

Antigravity CLI is available immediately. Google recommends installing it alongside Gemini CLI during the migration window to test workflows before the June 18 deadline. Official migration guides and video walkthroughs are forthcoming. Enterprise teams on Gemini Code Assist Standard or Enterprise licenses can evaluate the transition at their own pace — their existing access is uninterrupted.