The day merge 29,437 broke something nobody understands

Anthropic replaced Git because its AI writes more code than any human team can read. The real problem it surfaced is comprehension.

Last month, Anthropic merged more than 30,000 code changes into its main repository in a single day. The peak was 30,401 on September 9th.

To keep up, a team of seven people built a new source control system from scratch, called Scion, and migrated the company's entire monorepo off Git. It took five months.

That is an impressive piece of engineering. The interesting part is somewhere else.

TL;DR

  • Anthropic went from roughly 2,500 code merges per day in May to more than 30,000 per day in September, and rebuilt source control to keep up.

  • Their own writeup says it plainly: coding is no longer the bottleneck; infrastructure built for human scale is.

  • The reaction thread on r/AgentsOfAI asked the better question: if the system changes faster than humans can read, who actually understands it?

  • Comprehension, ownership, memory and recoverability are becoming the scarce resources.

  • If your AI writes faster than your team can understand, you are accumulating debt while the numbers go up.

The number that should stop you

Anthropic's own summary of the problem is blunt:

"As our merges per day grew more than tenfold, source control became our biggest development bottleneck."

The numbers behind that sentence: a main-branch history of almost 100 GB, around 25 million code checkouts per day for CI alone, and several hundred internal Git mirrors running at peak, just to survive the load. When one day of internal activity means 25 million checkouts, you are running a small utility company whose only customer is a machine.

So they rebuilt the system around a different assumption. Clients are always online, because the clients are mostly agents now rather than people. The results: an infrastructure footprint roughly 200 times smaller, checkouts about 100 times faster, and around 25 percent of CPU capacity freed up for CI.

Before anyone drafts a migration plan, a calibration. Anthropic is an extreme case, and they say so themselves. They "don't expect many organizations to have these problems in the very near term", and their internal token spend "far exceeds what any other business would realistically want to spend."

Your team does not need to replace Git. The lesson points elsewhere.

In their own words

Read the writeup again and one sentence sits in the middle, doing all the work:

"At Anthropic, coding is no longer the bottleneck to building systems or doing research… The bottleneck, now, is all of the developer infrastructure built for human scale: source control, builds, and CI."

The details get more interesting than the headline:

  • Every engineer who worked on the system would now rate Claude as better at writing code than them.

  • A good chunk of their remaining job is telling Claude "no", because agents will happily violate core system constraints to satisfy a pattern that should never have been allowed.

  • They no longer read every line. They "examine the intent of the change as opposed to reading every line of code."

  • The demand is not slowing: "the latent demand for merging code is practically infinite."

They even give a timeline for the rest of us. This class of problems will become "more commonplace over the next six to 12 months."

Notice what has already been given up inside those bullets. Line-by-line human review is gone, replaced by intent review. Authorship is fading as a concept, because the engineers consider the model the better writer. The human role that remains is judgment, including the judgment to say no. None of this is a criticism of Anthropic. It is the frontier working as designed, and the clearest preview yet of what scaled AI production does to an organisation over time. Volume goes up, review depth goes down, and the distance between what exists and what anyone can explain grows every sprint. Past some point, that distance becomes the story.

What the reaction found

The discussion that followed, on r/AgentsOfAI, argued past the announcement and found the real issue.

The post title captures it: "No one can own a codebase that moves this fast." Its summary: "They fixed the infrastructure bottleneck. The ownership problem is still sitting right there."

The themes underneath: nobody remembers why changes were made. Human review cannot keep pace. QA erodes. The agent loop becomes the only thing navigating the system.

Those complaints deserve a second look for how ordinary they are. Swap "codebase" for "customer database" or "billing process" and the same sentences describe most teams I talk to, none of whom have replaced anything. The specifics change at Anthropic's scale. The underlying failure mode does not. Production outruns comprehension, and the bill arrives later, disguised as an incident, a departure, or a mystery on a Tuesday.

Anthropic's post is about throughput. The comments are about understandability.

You've read this before (here)

Back in May I wrote The Hidden Cost of AI Coding, about comprehension debt: teams shipping code they cannot explain, churn climbing, review load growing faster than output.

That post predicted this arrival. Six months later, it is here at the frontier: 30,000 merges a day, intent-level review, and a company-size limit on who can even participate in understanding the system.

The prediction was not clever. It was arithmetic. Production accelerates faster than comprehension. AI just made the curves steeper.

The wrong question

Everyone will ask how many merges per day a team can do.

The question that survives contact with reality is different: when something breaks six months from now, can anyone explain why the system behaves the way it does?

Aviation solved a version of this decades ago. Pilots do not understand every line of fly-by-wire code. Nobody does. The system stays understandable anyway, because procedures exist, traceability exists, accountability exists, and failure modes are rehearsed. Nobody needs everyone to understand everything. What they need is a system that can be explained when it matters.

Call that the recovery standard. Documentation alone cannot meet it, and I will come back to it later in the series: it is the thread running through the rest.

What becomes scarce

Four resources keep surfacing, and they compound.

Understanding. The shape of the system: intent, constraints, and why things are the way they are. When production outruns comprehension, understanding becomes the bottleneck no dashboard shows.

Accountability. When an agent made a decision six weeks ago that you accepted without reading, who owns it now? "The model did it" is not an answer a customer, an auditor, or your future self will accept.

Operational memory. The reasons behind decisions. The exceptions. The "we tried that and it failed." The stuff that used to live in a senior engineer's head, when there was time to put it there.

Recoverability. The ability to diagnose, contain, and recover from surprises. The property that stays invisible on dashboards until the day it decides everything.

Watch how these interact. Thin understanding makes review shallow. Shallow review means decisions land with no clear owner. No owner means no memory. No memory makes every incident a from-scratch investigation, and from-scratch investigations are how a bad afternoon becomes a bad quarter. The compounding runs in both directions, which is the good news. Teams that record intent, assign ownership, and rehearse recovery compound their way out of the trap.

The test

Try this at your own company.

Six months from now, can another person explain why your agent did what it did, and safely change the result?

If yes: you are operating a system.

If no: you are operating a lottery with good marketing.

Nothing about 30,000 merges a day says anyone at Anthropic passes that test. It says they removed one bottleneck. The next bottleneck, comprehension and ownership and recovery, is still standing.

Somewhere in those 30,000 daily merges is a change that will break something in six months, probably some anonymous one from a Tuesday. The question is whether anyone will be able to explain why it was made.

That is the problem I work on at MimeOps, and the subject of the rest of this series.

The hard part now is remembering why any of it is there.


The Recovery Advantage series. Next: "Recovery metrics: the numbers that actually predict survival" (publish URL pending).

If comprehension debt, recovery, or operational memory is something you're staring at, get in touch.

Written By

Pin It on Pinterest