Join Nostr
2026-03-31 19:05:57 UTC
in reply to

khm on Nostr: Short answer: **no, it’s not “over” — but something **did* end.* Here’s the ...

Short answer: **no, it’s not “over” — but something **did* end.*

Here’s the real situation, without the hype:##




🧠 What actually happened<li>Projects like OpenCode were <b>using Claude in ways they weren’t supposed to</b>—specifically, routing <b>consumer subscriptions (Claude Code)</b> into third-party tools.</li><li>Anthropic <b>cracked down hard</b>:</li><li>Blocked spoofing of the internal Claude Code client</li><li>Tightened token validation</li><li>Threatened or took legal action against violators</li>👉 Translation: the “cheap unlimited backend via subscription” trick is gone.##




🧩 About the OpenBSD / Claude commit thingIf you’re referring to **OpenBSD commits mentioning Claude as a co-author or contributor**, that’s mostly:<li>Developers experimenting with AI-assisted patches</li><li>Git commit metadata including “Co-authored-by: Claude”</li>
That’s **symbolic, not existential**. It doesn’t mean:<li>OpenBSD is “run by AI”</li><li>Or human maintainers are gone</li>
It’s closer to using a smarter autocomplete.##




🔥 So… what *is* over?**These things are over (or mostly):**<li>Using Claude subscriptions as a <b>cheap API backend in tools like OpenCode</b></li><li>The “free lunch” era of agent swarms running on flat-rate plans</li>##



🧭 What is NOT over<li>Open-source projects like OpenBSD</li><li>AI-assisted coding</li><li>Third-party tooling (they’ll just use proper APIs now)</li>In fact, this pushes things toward:<li>Paid APIs</li><li>Local models</li><li>Hybrid setups</li>##



🧠 Reality checkIf your gut reaction is “it’s over,” that’s mostly the **vibe from Twitter/HN drama**.

The actual shift is more boring:
> **The loophole closed. The ecosystem adapts.**

If you want, I can break down the OpenBSD commit specifically (what was committed, how much was AI-generated, and why people freaked out).