Anthropic just moved its main codebase off git. A team of seven people built their own version control from scratch and called it Scion. Git runs pretty much every software company on earth, so why would anyone leave it? The short answer: machines forced the move, and a lot of those machines are AI agents, like the ones you're probably using right now.
How git thinks
Linus Torvalds and the Linux crowd built git in 2005, and one of their main goals was for it to be fully distributed. Every copy is a full copy: when you clone a repo, you get every file and the whole history on your laptop. You can commit on a plane with no internet, and if somebody's server goes down, you keep working. Git was built for people working apart, each with their own copy.
Anthropic's repo
Anthropic's repo is nothing like a copy on your laptop. According to Anthropic's post, its main-branch history alone is almost 100 GB. Their test machines pull around 25 million checkouts a day, and none of that is a person at a laptop. On top of that come agents and research jobs that are online all the time. Anthropic did the math: if every checkout pulled a normal git copy, that would be over 600 PB of traffic a day (a calculation, not a measurement).
The patches
For a while they patched around it. Shallow clones skip the old history. Sparse checkouts grab only the folders you need. At the peak they ran several hundred mirrors whose only job was to hand out code. But the number of changes merged every day kept climbing, so the patches kept breaking: the mirrors fell behind the latest code, and even simple things like finding who changed a line got hard on a partial copy.
The real problem
The patches were never going to work, because the problem was git itself. Git assumes everyone has their own full copy and works offline. Anthropic had one giant repo, and almost everything pulling from it was an agent or a job that never goes offline. In Anthropic's words, "The properties that make git excellent for distributed, offline work were actively undermining our ability to scale as the repo grew." Git was built for laptops, and their users are agents.
Scion
So they flipped it around. In Scion, the server does almost all the work and the machines around it stay thin:
- A commit happens on the server, so there's nothing to push.
- A machine downloads a file only when something actually opens it.
- Some jobs don't even need that: they ask the server a question, like which change broke this test.
- There's no full copy of the repo laid out anywhere, not even on the server. The server keeps the pieces, and each change is a small record pointing at the pieces it touched.
The bet: if the server does the work, the agents can go as fast as they want.
Did it hold up?
By Anthropic's numbers, checkouts that took minutes now take seconds, and Scion runs on about 200 times less hardware than the git mirrors did. Seven people moved everything over while the merges kept piling up: about 2,500 merged changes a day in May 2026, over 30,000 by September.
The catches
Every one of those numbers comes from Anthropic's own post, and since Scion isn't public, nobody outside can check them. The ideas aren't new either: Google ran Piper, one central repo for tens of thousands of developers, and Meta built Sapling and Mononoke. People said those projects deserved more credit, and two days after the post went up, Anthropic added it.
Will git break for you?
Probably not yet: you'd need a giant repo and a swarm of agents to hit this wall, and Anthropic itself says Scion "is by no means a suitable replacement for git for general use." But they expect this kind of problem to become more common over the next six to twelve months, because more and more code is going to come from agents. Git was built for people with laptops, and the next users of your repo might not be people at all.
Would you move off git if you ran a swarm of agents? Tell us in the comments or in the Discord.
Top comments (0)