GoKawiilThe Claude Code Leak Apr 1, 2026 | 6 min read
Much of the tech world is gushing about the accidental leak of Claude Code’s source code yesterday, but for different reasons than I find it interesting. I began jotting down my thoughts and came up with five distinct observations that had little to do with the leak itself, and more about what it tells us.
1. The Code Is Garbage
Tired: Omg the Claude Code leak is a bunch of vibe coded garbage Wired: Vibe coded garbage can get you to $2.5 billion annualized recurring revenue in under a year if the product market fit is there — Joe Fabisevich (@mergesort.me) April 1, 2026 at 10:25 AM
Claude Code is a beloved product, to the point where developers, designers, product managers, marketers, and even CEOs are obsessed with it! And yet the code that powers Claude Code is kind of garbage. So of course the first thing people did was point and laugh. But step back for a second and think, what does that tell us about the actual value of code?
I argued in AI Agents Are Starting To Eat SaaS (Really) that the barrier to entry for creating a product is going down. That seems like a statement about toy apps like todo lists and habit trackers — but it applies to all software. The success of Claude Code and Cursor at the higher end of the market shows that even the people pickiest about their software (developers) will use your software regardless of how good the code is.
Many software developers have argued that working like a pack of hyenas and shipping hundreds of commits a day without reading your code is an unsustainable way to build valuable software, but this leak suggests that maybe this isn’t true — bad code can build well-regarded products.
2. It’s Not About The Code
It should serve as a warning to developers that the code doesn’t seem to matter, even in a product built for developers. This interview with Boris Cherny (the creator of Claude Code) was eye-opening for me. He describes how they build software at Anthropic and explains why the code matters — just not in the way developers typically assume. What matters is what the code does, not how it does it at the character-by-character level. Anthropic isn’t only building better systems to write better code, they’re building better observability systems to monitor the effects of code changes.
Imagine you’ve built a feature and now it’s time to QA it. You notice that an email textfield doesn’t respond well to the @ character, so you go back to the code, read it, and with enough debugging you figure out a fix. But that doesn’t scale as well as a system that yells at you to say “users can’t log in right now”, and then goes back to automatically change or revert the code that broke your auth flow. If you can build a good self-healing system and are willing to take on a little risk of things breaking as you go, you can move a whole lot faster — not just a bit.
... continue reading