#version-control · Cascadity

MVMaker Views #anthropic #Hacker-News #maker #version-control

Anthropic replaced git for its monorepo after merges jumped to 30,000 a day

What happens to developer infrastructure when AI writes most of the code.

Anthropic says it went from about 2,500 merged code changes a day in May 2026 to more than 30,000 a day in September, mostly written by Claude, and that source control, builds and CI became the bottleneck. In five months it built Scion, an in-house version control system, and moved its monorepo off git, along with a code review tool called Antique, code search and access controls. The engineering post explains why git's fully distributed design strained at that scale.

Read it at the source

AnthropicRedesigning source control at Anthropic Independent ↗ Hacker NewsDiscussion: Redesigning source control at Anthropic Independent ↗

Cascadic Analysis 2

UndertowDelayed Consequence / False Success Problem

What hidden risk could pull against this, even if the news is good?

Anthropic went from about 2,500 to more than 30,000 merged changes a day, mostly written by Claude. At that volume, a mistake that slips through review can be copied into many later changes before anyone sees its effect.

UndertowLoss of meaningful human control as capability and autonomy increase

What hidden risk could pull against this, even if the news is good?

The post says the latent demand for merging code is "practically infinite" and every bottleneck removed leads to more code. Human review is one of those bottlenecks; the faster the system gets, the smaller the share of changes any person really reads.

Rabbit Holes 1

Monorepo

After exploring Redesigning source control at Anthropic, the setup that strained is Monorepo.

Keeping many projects' code in one repository, as Google, Meta, Microsoft and others do at very large scale.

Wikipedia · Wade · 5 min

0