Every CI/CD pipeline, shell script, and IDE integration that calls the gemini command stopped receiving responses today, June 18, 2026, as Google ended service for all free, Google AI Pro, and Ultra subscribers — 30 days after the company announced the decision at Google I/O. In its place, Google is pushing Antigravity CLI, a closed-source Go binary invoked as agy, built to run asynchronous multi-agent workflows that Gemini CLI’s single-agent TypeScript architecture could not support. The transition arrived without a grace period, and for the 105,000-strong GitHub community that helped build Gemini CLI over the past year, the replacement comes with fewer rights, tighter quotas, and no source code.

What Stopped Working Today

At the moment Google’s auth endpoint switched over, every gemini command for affected accounts returned HTTP 410 Gone. That covers all Google AI Pro and Ultra subscribers, free-tier users, and individual Gemini Code Assist users. Enterprise customers on Gemini Code Assist Standard or Enterprise licenses are explicitly exempted and retain access to both Gemini CLI and Antigravity CLI indefinitely. Individual users who want to keep the legacy tool need a paid Gemini Enterprise Agent Platform API key.

The scope extends beyond interactive terminal use. Any automation that calls gemini directly — GitHub Actions workflows, Makefile targets, Docker containers, cron jobs — is broken now. Gemini Code Assist for GitHub is affected separately: new organizational installations stopped on June 18, with full request serving ending in the weeks that follow, approximately mid-July.

Why the Architecture Required a Full Rewrite

Google’s stated rationale is not purely commercial. Gemini CLI was built as a TypeScript application running a ReAct (reason-and-act) loop: one agent, sequential steps, a terminal session that locked while the agent worked. The underlying Node.js event loop processes one task at a time and passes control between callbacks — a design suited to interactive prompts but not to the kind of large-scale background refactoring or parallel research tasks that have become standard in agentic developer workflows.

Antigravity CLI addresses this through a fundamentally different architecture. Built in Go, it uses asynchronous subagent orchestration: a manager agent receives the goal, decomposes it into subtasks, and spawns dynamic subagents in parallel — each with its own isolated context window, tool set, and model configuration. The isolation matters technically: a single-agent system accumulates context across every step of a complex task, degrading reasoning quality as the context window fills. Parallel subagents with isolated windows sidestep that problem by keeping each agent focused on a discrete subtask, then merging diffs back into the main session when finished. Google describes the practical ceiling as around four to five simultaneous subagents before performance degrades. The Go binary also provides sub-millisecond startup times — a material improvement over Node.js startup overhead for developers who invoke the CLI frequently in scripted workflows.

The multi-agent architecture also explains why the desktop app, CLI, and SDK all share the same agent harness: improvements to the underlying planning and tool-calling system propagate automatically to every surface rather than requiring independent backport work per product.

👉 Read more: 317056 Google closed Gemini CLI to enterprise-only

The Quota Cliff Nobody Put in the Headline

The most immediately damaging change for developers running automation is not the binary rename — it is the quota. Gemini CLI offered approximately 1,000 free requests per day. Antigravity CLI’s free tier is capped at roughly 20 requests per day, a 98% reduction. Multiple users in the Antigravity CLI issues tracker reported exhausting the weekly quota within a handful of prompts. The quota also shifted structure: Gemini CLI reset daily; Antigravity CLI resets on a weekly compute basis, meaning a developer who burns through the quota on Monday is locked out until the following Monday, not until Tuesday.

For developers who used Gemini CLI’s free tier to power meaningful CI automation — the population the 1,000-request daily limit was specifically designed to serve — migrating gemini to agy without accounting for this change will break pipelines silently on the first night they run.

The Silent CI Failure

Beyond the quota, migration guides have flagged one specific technical trap that breaks CI pipelines without producing an error message. Gemini CLI stored Model Context Protocol (MCP) server configuration inline inside settings.json. Antigravity CLI expects a separate mcp_config.json file, and the url field on each server entry was renamed to serverUrl. The agy plugin import gemini command handles most of the migration automatically, but it does not touch existing CI and automation scripts, and the MCP config field mismatch fails silently — producing no terminal error while requests silently stop routing. Any team that ran gemini in CI with a custom MCP server should verify the mcp_config.json migration manually before cutting over.

What a License Does Not Protect

The community anger around this transition is grounded in a specific governance argument that the open-source licensing discussion consistently misses. Gemini CLI launched in June 2025 under the Apache 2.0 license — a permissive license that allows anyone to fork, modify, and redistribute the code. Over the following year, external contributors submitted and had merged 6,000 pull requests, building features, fixing bugs, and growing a project that accumulated 105,000 GitHub stars. The repository was donated to the Linux Foundation before the shutdown announcement.

What the Apache 2.0 license did not protect was continued API access. The code remained public; the infrastructure that made the code useful stopped serving requests for anyone who did not pay. Christine Hall, who has covered free and open-source software since 2002, described the move at FOSS Force as “a new twist on a game that’s become increasingly common in recent years,” noting that the shutdown “only affects open source users. It doesn’t happen for those who pay for the product.”

Arnaud Le Hors of IBM, who co-authored the Linux Foundation’s Model Openness Tool framework and presented it at Open Source Summit North America 2026 in Minneapolis, put the structural problem plainly: a tool can score highly on code availability and still fail on operational independence — the ability to actually run what you helped build. The Gemini CLI case became the framework’s first public exhibit.

There is a legal dimension that received less attention. Gemini CLI’s CONTRIBUTING.md required all contributors to sign a Contributor License Agreement before their pull requests could be merged. Under Google’s CLA, Google holds a perpetual, worldwide, irrevocable license to use every line of contributed code — including incorporating it into proprietary successor products. The 6,000 developers who contributed to Gemini CLI did so knowing the code was Apache 2.0, but their signing of the CLA meant Google faced no legal barrier to building Antigravity CLI on top of their work. As contributor @lingyaochu wrote in the GitHub discussion thread: “That’s what you done, Google, open source Gemini CLI, get developers contribute to this, and then migrate the code to a close source project.”

Developer Andrea Alberti, whose 27-commit pull request was merged on the same day as the shutdown announcement, described the experience directly: “Essentially working for free on a code base that will only be used in enterprises?”

Migration Options

Developers whose pipelines broke this morning have three main paths forward.

Antigravity CLI is Google’s own replacement, available at antigravity.google. The agy plugin import gemini command handles most standard migrations automatically, renaming config files and importing extensions. Migration documentation is live at antigravity.google/docs/gcli-migration, with video walkthroughs promised in coming weeks. The tool coexists with Gemini CLI on the same machine during the transition window. The key steps: rename GEMINI.md to AGENTS.md, move .gemini/skills/ to .agents/skills/, update every gemini invocation in scripts to agy, and manually migrate mcp_config.json if using MCP servers.

Claude Code is Anthropic’s terminal-native agentic coding CLI and the migration path recommended most frequently by migration guides for developers who want a tool with a similar workflow pattern. It is included with Claude Pro ($20/month), Max 5x ($100/month), and Max 20x ($200/month) subscriptions, with interactive usage counting against standard subscription limits. Programmatic usage via claude -p and the Agent SDK draws from a separate monthly credit pool, a billing change that took effect June 15, 2026.

Aider is a fully open-source alternative under the Apache 2.0 license that remains community-governed, with no vendor lock-in risk. For developers who chose Gemini CLI specifically because of the open-source license and want to avoid repeating the same governance exposure, Aider represents the cleanest structural alternative — its code, governance, and backend model choice all remain under the developer’s control.

What the Lesson Actually Is

The durable lesson from the Gemini CLI transition is not that Google is uniquely untrustworthy, or that open-source licenses are worthless. It is that a license governs code, and infrastructure is not code. Gemini CLI was open source in a meaningful sense — the repository was real, the contributions were real, and the Apache 2.0 license was not a fake. But the tool’s practical utility depended entirely on Google’s backend: the authentication, the API, the quota system. When Google decided to redirect that infrastructure, the license provided no protection.

The relevant structural protection — the one that actually constrains a corporate sponsor from unilaterally redirecting a project — is independent foundation governance: projects donated to the Apache Software Foundation, the Linux Foundation, or the Cloud Native Computing Foundation with genuine independent oversight, not merely repository custody. Gemini CLI’s donation to the Linux Foundation came before the shutdown announcement, but repository custody alone is not governance. The pattern that protects contributors is one where the foundation controls the trademark, the roadmap process, and the dispute resolution path — not just a license file.

For any developer choosing a cloud-dependent AI tool today, the questions that matter are not “what is the license?” but “who controls the API keys, who controls the quota, and what contract governs how quickly that access can be revoked?”

Frequently Asked Questions

Is Gemini CLI permanently gone?

Not for everyone. Enterprise customers on Gemini Code Assist Standard or Enterprise licenses, and developers with paid Gemini Enterprise Agent Platform API keys, retain full access to Gemini CLI indefinitely. The shutdown today affects free users, Google AI Pro subscribers, Google AI Ultra subscribers, and individual Gemini Code Assist users. The Apache 2.0 code base remains publicly accessible on GitHub, but without Google’s backend infrastructure, it cannot be run as a functional tool without independently connecting a compatible large language model.

What are the best Gemini CLI alternatives for developers who want to avoid vendor lock-in?

The clearest alternative for governance-aware developers is Aider, which is community-governed, fully open-source under Apache 2.0, and carries no single-vendor infrastructure dependency. Claude Code is the most commonly recommended drop-in replacement for Gemini CLI’s interactive workflow patterns. For developers staying in Google’s ecosystem, Antigravity CLI is the official path, but its free tier now allows approximately 20 requests per day — compared to Gemini CLI’s 1,000 — so volume automation must be re-evaluated.

Why does an open-source license not protect against this kind of shutdown?

An open-source license — including Apache 2.0 — governs the software code, not the cloud infrastructure that runs it. Contributors to Gemini CLI also signed a Contributor License Agreement granting Google a perpetual license to use their code in any product, including proprietary ones. When Google ended API access for non-enterprise users, it shut down the infrastructure, not the repository. The code remains available; the authentication backend that makes it respond does not. The protection against this kind of shutdown is not a more restrictive license — it is independent governance, in which a foundation that is not the corporate sponsor controls the project’s operational continuity.

Is Antigravity CLI technically better than Gemini CLI?

In specific ways, yes. The Go-based architecture delivers faster startup times and enables asynchronous multi-agent workflows that Gemini CLI’s sequential Node.js design could not support — a genuine engineering upgrade for teams running complex background refactors or parallel research tasks. The tradeoff is a 98% reduction in free-tier request capacity, closed-source code that contributors cannot inspect or improve, and incomplete feature parity at launch. Google’s own announcement stated there “won’t be 1:1 feature parity right out of the gate” and has not committed to a timeline for when parity will be reached.