Claude now writes 80%+ of Anthropic's production code, and Anthropic wants a pause button

The number that should stop you: as of May, Claude authored over 80% of the code merged into Anthropic's production codebase. In early 2025 that figure was under 10%. Engineers there now ship roughly 8x more code per quarter than they did in the 2021 to 2025 baseline. That's from a June 4 report called "When AI Builds Itself," written by Anthropic's Jack Clark and Marina Favaro. Source: VentureBeat

I want to be careful here because 80% is the kind of stat that gets quoted out of context. "Authored by Claude" doesn't mean nobody reviews it. It means the keystrokes come from the model and a human approves, edits, and integrates. That's exactly how I work in my personal projects. The thing is, when the company that builds the model says its own engineers crossed 80%, the gap between "early adopter" and "everyone else" just got a deadline attached.

The other half of the report is stranger. The same authors who disclosed the productivity numbers are arguing the industry needs a coordinated, verifiable way to slow down or temporarily pause frontier development if systems start improving themselves faster than we can manage. A pause button. From the company shipping the fastest. You can read that as genuine concern or as regulatory positioning, and honestly I think it's both. They're documenting recursive self-improvement happening inside their own walls and saying "we might need to be able to stop this."

What builders should actually do: stop treating AI code authorship as a novelty metric and start treating it as a workflow you have to get good at, fast. The skill that separates people now isn't "can you prompt the model." It's whether your review process, your test coverage, and your taste can keep up with 8x the output. More code merged means more code to be wrong. If you're not building the verification layer, you're just accumulating liability faster.

The pause-button stuff I'd file under "watch, don't act." There's no mechanism, no standard, no enforcement. It's a position paper. But pair it with the rest of today's stories and you see why it's there. When Claude writes Claude's code, and Vercel's agents run Vercel, the feedback loops get short enough that "who's actually in control" stops being a philosophy question.