Anthropic has built its public identity around the winning idea that it’s the careful AI company. It publishes detailed work on AI risk, employs some of the best researchers in the field, and has been vocal about the responsibilities that come with building such powerful technology — so vocal, of course, that it’s right now battling it out with the Department of Defense. On Tuesday, alas, someone there forgot to check a box.

It is, notably, the second time in a week. Last Thursday, Fortune reported that Anthropic had accidentally made nearly 3,000 internal files publicly available, including a draft blog post describing a powerful new model the company had not yet announced.

Here’s what happened on Tuesday: When Anthropic pushed out version 2.1.88 of its Claude Code software package, it accidentally included a file that exposed nearly 2,000 source code files and more than 512,000 lines of code — essentially the full architectural blueprint for one of its most important products. A security researcher named Chaofan Shou noticed almost immediately and posted about it on X. Anthropic’s statement to multiple outlets was nonchalant as these things go: “This was a release packaging issue caused by human error, not a security breach.” (Internally, we’d guess things were less measured.)

Claude Code isn’t a minor product. It’s a command-line tool that lets developers use Anthropic’s AI to write and edit code and has become formidable enough to unsettle rivals. According to the WSJ, OpenAI pulled the plug on its video generation product Sora just six months after launching it to the public to refocus its efforts on developers and enterprises — partly in response to Claude Code’s growing momentum.

What leaked was not the AI model itself but the software scaffolding around it — the instructions that tell the model how to behave, what tools to use, and where its limits are. Developers began publishing detailed analyses almost immediately, with one describing the product as “a production-grade developer experience, not just a wrapper around an API.”

Whether this turns out to matter in any lasting way is a question best left to developers. Competitors may find the architecture instructive; at the same time, the field moves fast.

Either way, somewhere at Anthropic, you can imagine that one very talented engineer has spent the rest of the day quietly wondering if they still have a job. One can only hope it’s not the same engineer, or engineering team, from late last week.