On May 19, at Google I/O, Andrea Alberti watched her 27-commit pull request get merged into the Gemini CLI repository. The same day, Google announced the tool would stop working for individual developers on June 18.
"Essentially working for free on a code base that will only be used in enterprises?" she wrote. Hers wasn't an isolated case. Over the tool's year under Apache 2.0, the community contributed 6,000 merged pull requests. Google cited those contributions as evidence of the project's success. Then it locked the door.
Today is June 18. The door is locked.
The Graveyard Merge
On DEV Community, developer Himanshu Kumar told a sharper version of the story. His PR #19881 was merged — and 24 hours later, the project became a cemetery. He titled his post "My PR Merged Into a Graveyard."
The GitHub discussion thread collected 143 thumbs-down against 4 cheers within 24 hours. On Hacker News, the top comment read: "Fool me once, shame on you. Fool me 305+ times, shame on me" — referencing killedbygoogle.com.
But the Gemini CLI shutdown isn't a Google story. It's a pattern story. It landed on the same calendar as two other moves:
June 1 — GitHub Copilot switches to token-based billing. 900 downvotes, reports of 10-50x cost increases on day one.
June 15 — Anthropic splits Claude Code usage to credit pool at API rates.
June 18 — Google kills Gemini CLI for non-enterprise users.
Three vendors. Three weeks. Same direction. Where do displaced developers go?
Not to the Best Tool
The instinct is to compare features. Which tool has better code completion? Which scores higher on SWE-bench? Which has more sophisticated agentic workflows?
That's the wrong comparison. Developers aren't just choosing tools — they're choosing exposure. And the data says they know it.
The median developer now uses 3.1 AI coding tools simultaneously. Seventy percent use two to four. Fifteen percent use five or more. Multi-tool isn't a transition phase. It's the steady state — because no single vendor has earned enough trust to be the only dependency.
This is where OpenCode enters. Not as the best tool. As the one that can't be rug-pulled.
Trust Architecture
OpenCode passed 172,000 GitHub stars in June — the most-starred open-source AI agent. Eight million monthly active users. $25 million ARR. MIT license. Seventy-five-plus providers. Bring your own key.
None of these numbers explain why it's winning. Feature-for-feature, Claude Code is better. It has 54% market share among professional developers, 46% "most loved." OpenCode can't match its agentic orchestration, its context handling, or its raw code quality.
OpenCode wins on a different axis entirely:
| Axis | Vendor Tools | OpenCode |
|---|---|---|
| Can change pricing overnight | Yes | You pay providers directly |
| Can shut down | Yes (today) | MIT — forkable |
| Can throttle usage | 97% token cuts documented | No middleman to throttle |
| Can go closed-source | Gemini CLI just did | MIT — irrevocable |
| Can harvest contributions and lock you out | 6,000 PRs harvested | Contributions stay yours |
This isn't a feature table. It's a durability table. OpenCode competes on the axis that vendor tools structurally cannot.
The Replacement That Proves the Point
Google's replacement for Gemini CLI is Antigravity — a closed-source Go rewrite that doesn't have feature parity at launch. The migration experience has been instructive.
XDA Developers tried it for a week and quit. The reason: Pro users get locked out for seven full days after 20-30 minutes of active use. Token limits were cut from 300 million to 9 million input tokens per week — a 97% reduction — across four undisclosed quota cuts between December and March. Ultra subscribers paying $200/month get throttled too.
One user on Reddit: "I no longer use those Antigravity agents, only my Claude subscription. I do not want to feel like I am having a stroke every day."
The replacement for the open-source tool is a closed-source tool with less functionality, less access, and less trust — and you can't even report bugs because the internal reporting system is non-functional. The Gemini CLI shutdown isn't an anomaly. It's the mechanism working as designed.
The Institutional Response
The Linux Foundation noticed. At Open Source Summit North America in May 2026, they spotlighted isitopen.ai — a Model Openness Tool that scores AI projects across 17 components of the development lifecycle: model weights, training data, architecture documentation, inference code, licensing terms. It grades projects from Class 1 (closed) through Class 3 (fully open). No model yet meets the highest standard.
The framework was developed by researchers from Oxford, Columbia, and IBM. Its stated purpose: countering the practice of "claiming to be open source" while keeping critical components restricted.
Gemini CLI became exhibit A. The code was Apache 2.0. It was non-functional without a proprietary Google backend. The openness was structural theater — a developer acquisition funnel, not a commitment. The Linux Foundation is now building institutional infrastructure to make these distinctions visible before the next 6,000 PRs get merged into a project that can be shuttered.
The Valve
OpenCode gained 18,000 stars in two weeks during its January surge. The Gemini CLI shutdown is driving another wave. Migration guides proliferated in the weeks before today — "do this before June 18" — and the most common destination isn't Antigravity.
The tool wins not because it's better at writing code. Claude Code writes better code. Cursor has a better IDE experience. Copilot has deeper enterprise integration. OpenCode wins because when any of those three changes its pricing, throttles its users, or shuts down its predecessor, OpenCode keeps working. Same API keys. Same workflow. Different provider if you want.
The escape valve doesn't compete on quality. It competes on the thing that quality can't buy: the structural inability to betray the people who build on it.