Anthropic Scion Explained: Why Anthropic Replaced Git and What Developers Should Learn
I've used Git every working day for years. It's the one tool almost every developer agrees on. So when Anthropic said in October 2026 that it had moved its main codebase off Git, I wanted to know what actually broke. The answer isn't "Git is bad." The answer is that AI agents now write code faster than the tools around the code were built to handle.
What happened
On October 13, 2026, Anthropic's engineering blog described Scion, a version control system it built in-house. Scion replaced Git in the company's monorepo, which is the single repository holding most of its code. Alongside it, the team built Antique, a new code review tool, plus code search and access control for source code.
The trigger was volume. Daily merges grew from roughly 2,500 in May to more than 30,000 in September. Anthropic leans on Claude for coding much more than most companies, and their engineers said writing code was no longer the slow part. The slow parts were source control, builds and CI.
Why Git hit a wall
Git was designed in 2005 for the Linux kernel. Its core idea is decentralization. Every clone holds the full history, and you can commit, branch and merge offline. That's great for humans working on laptops. It gets painful when thousands of agents and CI jobs hit one giant repository all day.
- Every job pulls a lot of data. CI runners and agents need fresh checkouts constantly, and a big monorepo makes each one heavy.
- Mirrors pile up. At its peak, Anthropic ran several hundred internal Git mirrors to spread the load.
- The client does the work. Git computes merges, rebases and history on your machine. Multiply that by thousands of short-lived agents and it wastes a lot of compute.
How Scion is different
Scion flips the model. Clients are always connected and keep very little state. The server handles commits, merges, rebases and history queries.
| Git | Scion | |
|---|---|---|
| Model | Decentralized | Server-centric |
| Offline work | Yes | No, always connected |
| Merges and rebases | On your machine | On the server |
| Built for | Human developers | Huge monorepos with many AI agents |
| Available to you | Free, open source | No, internal only |
The results Anthropic reported
- Infrastructure footprint 200x smaller in CPU and memory than the old Git mirrors.
- CI and research checkouts in seconds instead of minutes.
- About 25% of CI CPU capacity freed up.
- Full migration by seven engineers in about five months.
One detail stood out to me. An early internal version of Claude Mythos Preview was asked to rewrite the pipeline that imports Git history into Scion. With no further instructions, it produced a version that used 20x less memory and ran 4x faster. The tool built to handle AI-written code was partly rebuilt by AI.
What this means for you
Anthropic says Scion isn't a suitable Git replacement for most teams, and it isn't releasing it. Don't migrate anything. But a few lessons apply to normal projects right now:
- Use shallow and partial clones in CI.
git clone --depth=1and--filter=blob:nonecut checkout time a lot on large repos. - Try sparse checkout.
git sparse-checkoutlets a job pull only the folders it needs. - Watch your merge queue. If you use Claude Code, Copilot or other agents, PR volume can jump fast. GitHub merge queues help.
- Plan for review load. More code means more review. Anthropic built a whole new review tool for this reason.
Anthropic expects more teams to hit these limits within six to twelve months, and it's asking GitHub, GitLab and the open source community to adopt the ideas that carry over, like server-side operations and better sync protocols.
FAQ
What is Anthropic Scion?
An internal, server-centric version control system that replaced Git in Anthropic's monorepo in 2026.
Is Scion open source?
No. Anthropic isn't releasing it. It's sharing the design lessons instead.
Should my team stop using Git?
No. Git is still the right choice for almost every project. Scion solves a problem very few companies have yet.