Gemini CLI will stop working from June 18, 2026
Google is retiring its open‑source Gemini CLI coding agent and pushing users to the new, closed‑source Antigravity CLI, prompting concerns about feature gaps, opaque quotas, and the loss of Agent Client Protocol support. Many developers see the move as another example of Google’s unstable product strategy and confusing branding around Gemini, Antigravity, and various AI plans, making it risky to build workflows on top of these tools. While some welcome consolidation on a single harness and note that enterprise access continues, others are canceling subscriptions or switching to rivals like Claude and OpenRouter to avoid lock‑in and sudden deprecations.
Transition from Gemini CLI to Antigravity CLI
- Gemini CLI support ends June 18, 2026; Antigravity CLI is positioned as its successor and is already available.
- Some see this as mostly a rename/unification of harnesses; others emphasize Antigravity is a different, heavier product with missing features.
- Enterprise users on certain Gemini Code Assist / Workspace licenses reportedly keep CLI access, but non‑enterprise plans lose Gemini Code Assist.
Features, Protocols, and Architecture
- Antigravity CLI is described as a large Go binary with its own browser control stack, sandboxing, Git, language detection, skills system, subagents, artifacts review, and telemetry.
- It appears to mirror many concepts from Claude Code (agents, skills, plugins, MCP), but current ACP support is missing, which worries people relying on it.
- Some developers prefer minimal/agnostic harnesses (e.g., MCP-based tools, Pi, Codex) over such complex, opaque agents.
Open Source vs Closed and Vendor Lock‑In
- Gemini CLI was Apache‑licensed open source; Antigravity CLI is closed, with only a minimal public repo.
- A “chance” of open‑sourcing Antigravity is mentioned but viewed skeptically.
- Several commenters see this as part of a broader shift away from open agents toward proprietary harnesses and tighter control over usage.
Quotas, Pricing, and Access
- Antigravity CLI appears to use weekly rather than daily limits; some users report hitting quotas that then take a week to reset.
- Many complain about opaque pricing, rapidly reduced quotas, and fragmented limits across Gemini CLI, Antigravity, and AI Studio now being consolidated.
- Access is restricted by geography and age; some users can’t subscribe at all, despite wanting to pay. Others use Gemini via OpenRouter to avoid Google billing.
Reliability, UX, and Product Quality
- Opinions on Gemini CLI are sharply split: some found it very useful; more describe it as slow, buggy, or “hot garbage.”
- Early Antigravity CLI/IDE experiences are often negative: UI glitches, sandbox networking issues, lost settings/extensions after updates, confusing documentation, and quota-related failures.
- A minority regard Antigravity as clearly superior and welcome centralizing on a single harness.
Impact on Developers and Trust in Google
- The one‑month migration window is seen as disruptive, especially for workflows depending on ACP or Gemini CLI behavior.
- Many cite this as another example of Google’s “graveyard” culture and say they now avoid building on Google AI tools or Google developer products generally.
- Some argue internal politics, reorgs, and prioritizing Google’s own needs over external developers drive these decisions.
Branding, Strategy, and Ecosystem Confusion
- Commenters criticize the proliferation and renaming of Google AI products (Gemini, Antigravity, Vertex, various “Pro/Ultra/Enterprise” plans), calling it incoherent and hostile to users.
- There is debate over branding: some think separating “Gemini” (models) from “Antigravity” (platform/harness) makes sense; others think abandoning the better-known Gemini name for a confusing new brand is counterproductive.
- Several say this volatility is why they stick with non‑Google providers (OpenAI, Anthropic, others) or open, vendor‑agnostic harnesses.