· 2 min read

Open Source is not a gift. It is a contract.

Google is shutting down Gemini CLI and replacing it with a closed-source tool. 100,000 stars, 6,000 contributions, hundreds of volunteers. Enterprise customers keep access. The community that built it gets 30 days. When the value lives in a proprietary API, even forking cannot save you.

Open Source is not a gift. It is a contract.
Gemini CLI shutdown by Google

Google just broke it and proved open source has a new single point of failure.

Open source is not a gift. It is a contract. Google just broke it.

This week at Google I/O, Google announced that Gemini CLI, its open source AI coding assistant, will stop working on June 18. That is 30 days from announcement to shutdown. The replacement is Antigravity CLI: closed source, proprietary, and by most early accounts, not ready.

Gemini CLI had 100,000 GitHub stars, 6,000 code contributions merged from hundreds of volunteers, and a license that explicitly allows anyone to use, modify, and share the code.

I used Gemini CLI from the start. I watched it improve, not just from Google's engineering, but from the community around it. People reported bugs, wrote extensions, fixed edge cases. The kind of investment that turns a tool into infrastructure.

Then Google changed the locks.

But there is a detail that makes it worse. Enterprise customers on paid licenses keep full access indefinitely. The individual developers, the contributors, the open source community? Cut off. The people who built the product are the ones losing access to it.

As one contributor asked: "What was the point of thousands of community contributions if we can't meaningfully benefit from or contribute to what comes next?"

And the replacement? Antigravity CLI is closed source with no public bug tracker and no documented security process. Early users report it cannot handle basic actions like resizing a window. The migration docs are full of broken links.

This is not an isolated incident. killedbygoogle.com tracks over 300 discontinued Google products. But killing a proprietary product is one thing. Shutting down a project that hundreds of people invested their unpaid labor in is a different kind of breach.

When corporations have pulled the rug on open source projects before, the community had a response: copy the code and keep developing it independently. When a major infrastructure company restricted its most popular tool's license, the community launched an independent version within weeks.

But that escape hatch does not exist here. Gemini CLI is just a "harness", a steering wheel. The engine, Google's AI models, stays locked inside Google's servers. You can copy the interface, but you cannot copy the intelligence it connects to. This is what dependency on a single vendor looks like when that vendor decides to walk away.

The real lesson is not that Google is unreliable. Everyone knows that. The lesson is about leverage: when you contribute to a corporate-controlled open source project, your influence disappears the moment the corporation changes direction. The license protects the code. It does not protect the community's investment.

If your workflow depends on a tool that exists at the pleasure of a single company, the question is not whether it gets shut down. It is when. What would it take for you to stop betting on something one company can kill with 30 days' notice?

Read next

A black server rack in a dim data center, its cables grown into the concrete floor like roots and cracking it, beside an empty hand truck.
Article Open Source Digital Sovereignty

Big Tech just priced its own lock-in.

A Big Tech lobby study says Europe's cloud sovereignty law will cost €115 billion. Most of it is the cost of undoing lock-in, and it grows every year you stay. Why Washington's pressure is nothing new, where buy-European falls short, and why open standards are the export worth building.

Kai A. Hartung
Kai A. Hartung
· 2 min read
A roller conveyor in a dim warehouse carries a long row of identical new cardboard boxes. Among them ride a few old, crumpled boxes patched with tape, one in sharp focus at the center.
Article Open Source Digital Sovereignty

The fix is out. Is it in?

Almost four years after a free fix shipped, about one in eight Log4j downloads was still a vulnerable version. Now AI has bank regulators counting the days. Why private copies slow the fix down, what the banks' new alliance changes, and the question to ask your IT team.

Kai A. Hartung
Kai A. Hartung
· 2 min read
A long till receipt listing licences, cloud, add-ons and contractors, torn off just below the word TOTAL.
Article Open Source Digital Sovereignty

The bill nobody can add up.

The Dutch government has a Linux desktop on trial, no new money for its digital autonomy plans, and no total for what it pays Microsoft. Leaving shows up as line items someone must sign for. Staying hides in budgets nobody adds up.

Kai A. Hartung
Kai A. Hartung
· 6 min read