Google recently merged the work of 6,000 community contributors to its Gemini CLI. Then they pulled up the drawbridge and told free users to kick rocks.
If that doesn't get your blood pumping, you haven't been listening.
What Happened
Google is deprecating Gemini CLI for free users and paid consumer subscribers, shifting them to a replacement tool called Antigravity CLI. Enterprise customers retain access to the tool. Everyone else, including the thousands of developers who contributed to it, gets a thank-you card and a locked door.
Approximately 6,000 community contributions were merged prior to the change. Six thousand PRs, bug fixes, docs improvements, and feature additions. All volunteered work, because those people saw value in the project.
The Playbook Is Always the Same
This is nothing new. The pattern is so obvious that there should be a Wikipedia page about it.
→ Step 1: Launch an open-source tool with big promises
→ Step 2: Let the community do massive amounts of free work
→ Step 3: Wait until the tool is mature and battle-tested
→ Step 4: Lock it behind an enterprise paywall
The community isn't the customer. The community is the unpaid QA team. The free R&D department. The marketing engine that gets developers emotionally invested so enterprises feel safe buying in.
"But You Should Have Known"
Yes, I can already imagine people saying that. "Oh well, it's Google after all. They destroy every other project."
That's a valid argument. But "you should have seen it coming" doesn't make it okay. It simply implies that we have accepted such exploitation to the extent that victims are held accountable for trusting a company worth a trillion dollars.
Contributing to corporate open source is a gamble. You're betting that the company's incentives will stay aligned with yours. And the house always wins. 🎰
The 6,000 people who contributed to this tool were not given any shares. They were not compensated. They didn't even get a vote on whether the tool they helped build would remain accessible to them.
What Devs Should Actually Do
I'm not suggesting you should never support corporate Open Source Software. That's unrealistic and honestly some of those projects do real good.
However, be cautious and well-informed.
→ Treat corporate OSS contributions as resume-building, not community-building
→ If a project doesn't have a strong independent governance model, assume the company will eventually rug-pull
→ Prioritize contributing to foundation-backed or truly community-owned projects
→ If you're going to contribute to BigCorp's repo, at least make sure the license protects forks
The Apache License, MIT, and the like do not prevent the code from being closed up again. However, the project itself, including the brand, infrastructure, and distribution, can certainly be taken away, which is precisely what occurred in this case.
The Bigger Problem
This goes beyond Gemini CLI. It concerns the overall interaction between big tech and the open-source community.
Companies get billions in value from open-source labor. The contributors get... exposure? A green square on their GitHub profile? Cool. Try paying rent with that. 😤
Every time this happens and we shrug it off, we tell the next company that the playbook works. That developers are an infinitely renewable resource who will keep showing up with free labor no matter how many times they get burned.
The Takeaway
Google leveraged the open-source community to develop, test, and refine Gemini CLI. But ultimately determined that only paying enterprise customers would have access to the final product. The 6,000 contributors were the scaffolding. And you tear the scaffolding down when the building is complete.
My question is: Is it reasonable for developers to ask for formal contribution agreements with guaranteed access clauses before contributing to corporate open source? If not, is the alternative to simply not contribute to tools owned by companies that have a history of being rug-pullers?
