What actually leaked — source code vs model weights

21:46how it happened was it is a little bit in the weeds, so I'll kind of keep it topical. Uh, there was a release of a new version of Claude code and on NPM, which is a package managing platform, there was a small uh, addendum that was added by one of their internal developers that had a 60 megabyte JavaScript source map. And you were able it basically you were able to use that to reconstruct the entire TypeScript project. So people were able to basically get 500,000 lines of the actual code base that is what Claude code is. >> Okay. >> Off across roughly 1,900 files. And what was

22:27fascinating to see was Korean developers, when they woke up, saw that this had happened, immediately pulled the package down, rebuilt Claude code, released it as basically a free open source version on GitHub, and it was the fastest-growing repo on GitHub in history, reaching 50,000 stars in 2 hours, >> Whoa. >> 100,000 like in the first day, and it is it is just exploded like wildfire. I think part of that was because people were confusing the model for Claude code. >> Oh, okay, I see. So they thought, oh, we just got the weights. Like, Oh, oh my god, the weights are public. Okay, got it. Okay. Early on people were like, oh, the weights went out. But it really is

23:08just that Claude code. They still have the crown jewels. And the irony of this story, there's a couple of things. It was basically an internal developer who screwed up with the release packaging. >> Yeah, someone's getting fired. >> They already got fired and they tweeted about it. >> Oh, okay, great. >> It's already on Twitter or X or whatever. And so that went out. And and I think it's it's the the speed in this space is astronomical. Uh because in less than a day, basically developers were able to wake up, recreate it not only in they did it like in >> Probably using Claude code. >> Exactly, exactly. And they recreated I think in JavaScript and then just built a version in Rust like

23:49immediately. And it's it's the ingenuity of developers now and the because they have a coding assistant tools, things can move very, very quickly. >> incredible. And so the wrapper around the model leaked, not the core model. >> model. Okay. >> Um but the other irony for for Anthropic is when you look at the personalities of all of the the between Google, OpenAI and Anthropic is the top three arguably. Anthropic has been very heavy on the sort of AI safety, you know, we are focused on that piece and security and all this matters. So for them to have be the first ones to have such a catastrophic leak of something fundamental is not

24:30really good for the brand. >> Mhm. Um especially when OpenAI just finished closing their highest the highest funding round venture capital fund round I think is $122 billion in the history of funding ever. Literally like a day or two before this happened. >> So the race is on. Um no, you're not just going to get and you know, Claude on your computer by default. But you know, Claude code is quite quite nice. >> Yeah. there's a lot of interesting insights in how they set up the harness around the model to make it practical. Uh-huh. Um that is going to continue to be used by developers uh outside of just using their their tools. And so I mean, I'm sure by now

25:11there's probably like a dedicated team at OpenAI that is like, "What's the best part of this that we can put into ours?" I'm sure. I'm sure. And it's it's funny there's a there's like an undercover mode or something that was a part of the leaked code base that was specifically a tool to prevent this stuff from happening. >> And clearly that didn't work. >> that also got leaked. Jesus. So, tough tough day for Dario Amodei. Uh keep fighting the good fight. AI safety is important. >> Yeah. Operational security is also important. Uh so, that's our story number two. I'm going to take a brief pause for some show notes. >> Mhm. If you love the show, everything you can do to support us is helpful, whether that's a like, a share, a

25:52comment, bring us up a journal club, the billionaire algorithm. We have to continue to fight to get awareness and relevance and all of that engagement really helps us get seen by more people. It continues to just be the two of us who are running this podcast. No advertisers at this moment in time. >> Mhm. Right? And we're doing it for the love of the game. Yeah. And so, um if you want to support us financially, uh you can go to ffpod.com/donate, and that is the place in which you can help support us in that way. But enough of all that nonsense, let's move to our third story. So, our third story is