Google discontinued Gemini CLI on June 18, 2026, replacing the open-source terminal agent with Antigravity CLI, a closed-source Go binary that dramatically reduces free-tier access. The move affects developers who built workflows around the original tool, which accepted over 6,000 community pull requests before being sunset. Free and Pro users now face a 98% reduction in daily request quotas, while the new tool's authentication system breaks existing CI/CD (continuous integration/continuous deployment) pipelines for some users.

What Happened to Gemini CLI?

Gemini CLI was an open-source terminal agent that allowed developers to interact with Google's Gemini models directly from the command line. The tool had become popular enough that the community contributed thousands of improvements over nearly a year. Google cited these contributions as evidence of success, then restricted the tool to enterprise-only access and replaced it with Antigravity CLI for everyone else.

The transition occurred without warning to individual developers. If you were typing "gemini" in your terminal last week, the command stopped working. The new tool requires users to invoke "agy" instead and authenticate through OAuth rather than API keys. While Google framed the change as an upgrade, the quota restrictions tell a different story.

How Severe Is the Quota Cut?

The numbers reveal the scope of the restriction. Gemini CLI gave free and Pro users approximately 1,000 requests per day. Antigravity CLI operates on a weekly compute-based cap that community reports estimate at roughly 20 requests per day equivalent. This represents a 98% reduction in available requests for free-tier users.

The quota trap extends beyond raw numbers. Antigravity CLI shares its weekly compute budget across the desktop app, command-line interface (CLI), and software development kit (SDK). If you use the Antigravity desktop app in the morning and the CLI in the afternoon, both pull from the same weekly bucket. One paid Pro user reported hitting "Individual quota reached" after just two prompts, a quota that previously survived over 1,000 code modifications in Gemini CLI.

What Technical Problems Are Developers Facing?

Beyond quota restrictions, Antigravity CLI introduced a critical authentication failure. Direct Google AI Studio API key authentication for headless environments appears broken, according to the source documentation. This is an active, unfixed problem that affects CI/CD pipelines relying on bare API keys for automation.

Google maintained core features from the original tool, including Agent Skills, Hooks, Subagents, and Extensions (rebranded as Antigravity Plugins). Multi-file editing and Model Context Protocol (MCP) server support remain present. However, the execution problems outweigh the technical improvements. Antigravity is genuinely faster due to its Go implementation versus Python, and the multi-agent architecture with dynamic subagents represents a legitimately interesting direction. The trust issue, however, overshadows these advantages.

Steps to Migrate From Gemini CLI to Antigravity CLI

• Install the new binary: Run the installation script for your operating system (macOS/Linux uses curl, Windows uses PowerShell), which places the "agy" binary in ~/.local/bin
• Authenticate with OAuth: Run "agy" and select OAuth on first launch, which opens your browser for Google consent and eliminates the need for.env files with API keys
• Import existing plugins: Run "agy plugin import gemini" to pull your MCP server registrations, allowed commands, and custom keybindings from the old tool, though you should test each plugin afterward
• Update CI/CD commands: Replace "gemini -p" prompts with "agy -p" equivalents, but verify that direct API key authentication works in your headless environment first

Why Are Developers Upset About This Change?

The core frustration stems from Google's use of open-source contributions to roadmap a proprietary replacement. Google accepted 6,000+ merged pull requests from community contributors to Gemini CLI, then cited those contributions as evidence of success before restricting the tool to enterprise-only access. The community noticed immediately, and GitHub issues filled with frustrated posts accusing Google of leveraging open-source work to build a closed-source product.

Enterprise customers retain unchanged access to Gemini CLI. Individual developers who built real workflows on it, including CI/CD pipelines and development automation, received a closed-source binary with a fraction of the quota and no clear fix for broken authentication. This pattern mirrors what critics call the "Google Graveyard," where the company discontinues tools that developers actively built upon.

The official announcement frames the transition as an upgrade. Usage reports and quota comparisons suggest otherwise. For light Antigravity CLI use involving occasional queries and small tasks, the tool may stay within quota limits, and the faster performance is a genuine improvement. However, developers who relied on Gemini CLI's 1,000-request daily free tier for real development work face a fundamentally different product.