Redesigning source control at Anthropic
The company says its internal merge volume made source control a development bottleneck.
TL;DR
- Anthropic says its daily code merges rose from about 2,500 in May 2026 to more than 30,000 by September.
- The company says it migrated to an in-house version-control system over five months as developer infrastructure became a constraint.
- The account is a company case study; it does not establish that the same approach would work for other engineering organizations.
Anthropic said its monorepo handled about 2,500 merged changes per day in May 2026 and more than 30,000 per day by September. It described the increase as a result of coding and research work moving faster with Claude-assisted workflows. [1]
The company says source control became a bottleneck alongside builds and continuous integration. Its engineering post describes a five-month migration to an in-house version-control system, but the article does not publish a full independent benchmark of reliability or operating cost. [1]
The post frames the change as a response to a particular scale of internal demand, rather than a general recommendation to replace Git. A Reddit discussion linked to the article focused on the reported merge rate and the trade-offs of building a bespoke tool. [2]
Details still open include the system’s long-term maintenance burden, how it handles failures and whether the reported throughput changes research or product delivery outcomes. The figures and performance framing remain Anthropic’s own account. [1]
Why it matters
The reported merge rate illustrates how AI-assisted code generation can shift bottlenecks from writing code to review, integration and developer infrastructure.
Editor's note
Company-reported internal metrics; no independent benchmark of the system was located.