The 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.

3. It’s About Product Market Fit

As always, product market fit is the only thing users care about. If the product works, very few people care how it works under the hood. Heck, most people don’t even have an inkling of what’s actually happening behind the scenes.

There’s always a chance that Claude goes to shit (or just goes down every day because Anthropic’s servers are under-provisioned due to poor demand prediction). If that happens, OpenAI can jump in with their equally good (if not better) model and leverage the ridiculous amount of servers they have to serve the latent demand. Or maybe Google will eventually figure out how to ship a good coding product. There’s plenty of opportunity here, and ultimately we’re supply-constrained in meeting consumer demand.

4. Copyright Is Still A Touchy Subject

The whole copyright situation is very funny to me, and feels a bit like Anthropic is getting a taste of their own medicine. But I think there’s more to it than just what comes around goes around.

The first thing Anthropic did when their code leaked was send a bunch of DMCA notices on Github to have the repos taken down. True to their committment to vibing, Anthropic ended up sending DMCA notices to forks of their own claude-code repo that hosts their skills, tutorials, and example code.

But then the clean room implementations started showing up. People had taken Anthropic’s source code and rewritten Claude Code from scratch in other languages like Python and Rust. The whole AI industry — Anthropic included — has been arguing that using AI to rewrite something is not derivative work and doesn’t violate copyright, because that is how they themselves train their models.

Now this part really does feel like Anthropic’s getting a taste of their own medicine. But my higher-level reading is that this further entrenches the idea that code should be free, just with a more libertarian bent than the Free Software Foundation expected.

5. This All Doesn’t Matter

All of this is interesting, but I think Claude Code’s source code being leaked won’t matter as much as people seem to think it will. The real value in the AI ecosystem isn’t the model or the harness — it’s the integration of both working seamlessly together. Anthropic could open source Claude Code tomorrow and it wouldn’t change a thing, because what people are paying for is the great results, not the underlying code. Codex has been open source since launch, and Gemini is too. Neither has captured Claude Code’s mindshare even though many people prefer Codex — because what Anthropic is selling is a complete service.

Lately I’ve been using the pi coding agent a lot, and I love it. Pi is a coding agent with just four tools: read, write, edit, and bash. It works with every major model provider — including Claude — and it works brilliantly. The reason is that it’s optimized for working through problems the way a developer would solve them — by writing code. This is a different approach to Claude’s abundance of tools, which goes to show there’s a diversity of ways to create an integrated experience across model and harness.

So… Where Does That Leave Us?

I’ve had to question the value of code a lot over the last couple of years, and this leak continues to reinforce the notion that I’ve vastly overestimated it my entire career. What matters is integration. Whether that’s product market fit or how well a model and harness work together, users have always cared about having their problems solved — solved well, really.

You can build something great by making it simple or complex, open or proprietary, but it has to work seamlessly. A clean codebase only matters if it delivers better results for users. This leak changes the perception of Claude Code more than it changes anything tangible, but perception is reality. And the reality is that the code was never what made Claude Code valuable in the first place — everything happening around the code matters more.