ANALYSIS

Anthropic Accidentally Takes Down 8,100 GitHub Repos in Botched Claude Code Takedown

M MegaOne AI Apr 2, 2026 3 min read
Engine Score 5/10 — Notable
Editorial illustration for: Anthropic Accidentally Takes Down 8,100 GitHub Repos in Botched Claude Code Takedown
  • Anthropic issued a DMCA takedown notice that inadvertently affected approximately 8,100 GitHub repositories, including legitimate forks of its own public Claude Code repository.
  • The takedown was triggered after a software engineer discovered that Anthropic had accidentally included source code for its Claude Code command-line tool in a recent release.
  • Anthropic’s head of Claude Code, Boris Cherny, acknowledged the mistake and retracted the bulk of the takedown notices, limiting the action to one repository and 96 forks.
  • The incident comes as Anthropic reportedly prepares for an IPO, where execution and compliance record will face heightened scrutiny.

What Happened

Anthropic accidentally caused thousands of code repositories on GitHub to be taken offline while attempting to remove copies of its Claude Code source code from the internet. According to TechCrunch, the sequence began on Tuesday when a software engineer discovered that Anthropic had inadvertently included access to the Claude Code command-line application’s source code in a recent release.

AI enthusiasts quickly shared the leaked code on GitHub, prompting Anthropic to issue a DMCA takedown notice. But because the targeted repository was part of a fork network connected to Anthropic’s own public Claude Code repository, the takedown swept across approximately 8,100 repositories, according to GitHub’s DMCA records. Many of the affected repositories were legitimate forks that had nothing to do with the leaked source code.

Why It Matters

The incident highlights the blunt-instrument nature of DMCA takedowns on platforms like GitHub, where fork networks can connect thousands of repositories. When a takedown targets a repository in a large fork network, it can cascade to all connected forks. Anthropic is not the first company to encounter this problem—similar issues have affected other organizations using GitHub’s DMCA process.

The timing is particularly sensitive for Anthropic. The company is reportedly preparing for an IPO, and incidents involving source code leaks and compliance missteps draw attention from prospective investors and underwriters. As TechCrunch noted, leaking source code as a public company would carry significant legal exposure, including potential shareholder lawsuits.

Technical Details

Claude Code is Anthropic’s command-line AI coding assistant, which has become one of the most popular developer tools in the AI ecosystem. The source code that was accidentally exposed gave outside observers a look at how Anthropic structures the application layer that sits on top of its Claude language model. The leaked code was cloned more than 8,000 times before the takedown, according to The Decoder.

Boris Cherny, Anthropic’s head of Claude Code, publicly acknowledged the error on social media. An Anthropic spokesperson told TechCrunch: “The repo named in the notice was part of a fork network connected to our own public Claude Code repo, so the takedown reached more repositories than intended. We retracted the notice for everything except the one repo we named, and GitHub has restored access to the affected forks.”

Who’s Affected

Developers who maintained legitimate forks of Anthropic’s public Claude Code repository temporarily lost access to their work. Open-source contributors expressed frustration on social media about having their repositories taken offline without warning. Anthropic’s reputation with the developer community—a critical constituency for a company that relies on developer adoption—took a hit, even though access was eventually restored.

What’s Next

GitHub has restored access to the affected forks following Anthropic’s retraction. The final takedown scope covers one repository and 96 forks containing the leaked source code. Anthropic will likely need to review its release processes to prevent future accidental source code exposure. The incident may also prompt broader discussion about how DMCA fork-network takedowns should be handled on collaborative coding platforms.

Share

Enjoyed this story?

Get articles like this delivered daily. The Engine Room — free AI intelligence newsletter.

Join 500+ AI professionals · No spam · Unsubscribe anytime

M
MegaOne AI Editorial Team

MegaOne AI monitors 200+ sources daily to identify and score the most important AI developments. Our editorial team reviews 200+ sources with rigorous oversight to deliver accurate, scored coverage of the AI industry. Every story is fact-checked, linked to primary sources, and rated using our six-factor Engine Score methodology.

About Us Editorial Policy