October 13, 2026 - Linkblog
Redesigning source control at Anthropic (source) This is a fascinating post from Anthropic detailing why and how they built a custom in-house alternative to Git, driven by an astonishing surge in their code change velocity over the past six months.
In May 2026, Anthropic merged an average of around 2,500 changes per day; by September, we were merging over 30,000 per day.
They included a chart illustrating these changes. I had Claude modify the chart (code here) to annotate Anthropic’s public model releases throughout 2026:

These reflect public release dates rather than when the models became available internally at Anthropic. I suspect the arrival of Fable/Mythos-class models was a key driver behind the dramatic spike in code output.
“Antique” is their new code review system. The version control system itself is called Scion, which looks to me like a modern reinvention of a Subversion-style centralized VCS. They were dealing with some staggering requirements:
The history of our main branch alone is nearly 100 GB, with a compressed working copy exceeding 25 GB. Before accounting for developer environments, agent sandboxes, or research jobs, we run roughly 25 million code checkouts a day just for CI. Pulling this naively would generate over 600 PB of Git traffic daily.
The new system was developed by a team of seven, taking just five months to complete a full migration away from Git.
As an aside, I’ve recently been experimenting with adversarial reviews in my own projects—prompting models to actively hunt for flaws (I often pit Claude and GPT against each other). This passage from the post resonated strongly with my experience:
Anthropic also makes heavy use of adversarial reviews. While exceptionally effective in many respects, it can suffer from myopia, requiring experienced engineers to steer Claude away from locally over-engineering around hypothetical problems.