Google Kills 105K-Star Gemini CLI and Replaces It With Closed-Source Antigravity

Google's Gemini CLI -- the open-source terminal coding agent that amassed 105,000 GitHub stars and thousands of community contributions -- is gone for most users as of today. Google replaced the 105,000-star open-source coding tool with Antigravity CLI, a closed-source Go binary that drops free-tier requests from 1,000 per day to roughly 20 and ships with an MCP config change that silently breaks CI pipelines. If your scripts or pipelines call the gemini command, they stopped working today with no grace period.

What actually changed

At Google I/O, Google announced it's consolidating its developer tooling under one brand -- Antigravity -- and retiring the standalone Gemini CLI and the Gemini Code Assist IDE extensions in the process. The transition is immediate and non-optional for most users.

• Gemini CLI and Gemini Code Assist IDE extensions have stopped serving requests for Google AI Pro and Ultra, as well as those using it free of charge using Gemini Code Assist for individuals.
• For Gemini Code Assist for GitHub, there will be no new installations on GitHub organizations and requests in the following weeks will stop being served.
• If your organization uses Gemini CLI or IDE extensions via a Gemini Code Assist Standard or Enterprise license, or through Google Cloud, your access remains unchanged.

Meet Antigravity CLI

The Google Antigravity ecosystem consists of a standalone desktop application (Antigravity 2.0) and a high-performance, Go-based terminal interface (Antigravity CLI), both powered by a unified shared agent harness designed for complex, multi-agent orchestration. The CLI binary is invoked as agy instead of gemini.

The headline technical upgrade is the shift from a single-agent model to what Google calls Subagents -- the idea that your main agent can spawn specialized worker agents that run in parallel. Instead of one AI doing everything, your main agent can now spawn specialized helpers to work in parallel. Google recently proved how powerful this is by tasking an agent team to build a functional Operating System from a single prompt. The three roles in that demo were:

• The Sentinel -- manages the project and structures intent
• The Worker -- writes actual code and runs builds
• The Auditor -- checks for "AI laziness" to ensure code actually works and isn't just a mock implementation

Built in Go, Antigravity CLI is snappier and more responsive. It orchestrates multiple agents for complex tasks in the background, letting you run large-scale refactors or research several topics without locking up your terminal session. Antigravity CLI also shares the same agent harness as Antigravity 2.0, ensuring that all future improvements to core agents are automatically applied wherever you use them.

Google co-optimized the Antigravity harness specifically for the Gemini 3.5 Flash model. While Flash is already fast, it runs up to 12 times faster inside Antigravity thanks to specialized inference tricks.

How to migrate right now

The official announcement says Antigravity CLI will automatically detect your existing Gemini CLI directory during installation and carry over your settings. Here are the install commands:

# macOS and Linux
curl -fsSL https://antigravity.google/cli/install.sh | bash
# Windows PowerShell
irm https://antigravity.google/cli/install.ps1 | iex
# Windows Command Prompt
curl -fsSL https://antigravity.google/cli/install.cmd -o install.cmd && install.cmd && del install.cmd

What gets migrated automatically:

• Skills -- custom and installed skills are imported automatically
• MCP Servers -- all configured Model Context Protocol servers (the standard for connecting AI agents to external tools) are migrated, though they now live in a dedicated mcp_config.json file
• Agents -- existing agent profiles and setups remain intact
• Memory -- full compatibility with existing gemini.md files is preserved

For workspace-specific skills, you'll need to manually move them to the new .agents/skills folder. The full migration guide is available at the official Antigravity docs.

The open-source bait-and-switch problem

This is where the community backlash gets real. Gemini CLI was Apache 2.0 licensed and fully open-source. The successor is Antigravity CLI -- a closed-source rewrite with a new binary, a new config layout, and a quota model that quietly trades daily limits for weekly ones. Surf over to the Antigravity CLI GitHub repo and all you'll find is a changelog, a readme, and a GIF.

Google's own announcement cited community contributions as evidence of the project's success -- then used that success to justify consolidating into a closed-source replacement. Developer Andrea Alberti had a 27-commit pull request merged the same day as the shutdown announcement. Her response: "Essentially working for free on a code base that will only be used in enterprises?"

Gemini CLI Lead Product Manager Dmitry Lyalin took to GitHub to make an announcement detailing some additional info about the forced CLI tool migration, and the comments are rife with people frustrated by the move. No small portion of the vitriol is targeted at apparent usage limits, with multiple people reporting they'd hit their weekly quota with just a couple of requests.

What this means for your workflow

Any CI/CD pipeline, shell script, or automation that calls the gemini command will break with no warning and no grace period. The most urgent action item is auditing any automation that shells out to gemini and replacing it with agy. Beyond the binary rename, the MCP config path change is the most likely silent failure in existing pipelines.

For individual builders who relied on the generous free tier, the calculus is harder. For individual builders, the practical migration path is Claude Code for terminal workflows or Aider for full open-source control. Google's Antigravity CLI is available now, but the dramatically reduced free quota makes it a much less attractive sandbox for experimentation than Gemini CLI was.