Anthropic Scion version control graph with the headline Anthropic Scion replaces Git

Anthropic Scion: Why Anthropic Dropped Git for Its Own Source Control

Anthropic has built its own version control system, called Scion, and moved its entire monorepo off Git. Anthropic Scion exists because AI-written code pushed the company past 30,000 merges a day, and Git’s usual setup couldn’t keep up. You can’t download it, though.

The news comes from an Anthropic engineering post, which The New Stack covered on October 15, 2026. Here’s what’s confirmed, what’s only Anthropic’s claim, and what it means for your own projects.

Here are the facts that matter most, so you can skim first:

  • Scion is Anthropic’s in-house source control system, revealed the week of October 15, 2026.
  • Daily merges hit 30,000+ in September 2026, up from about 2,500 in May.
  • Anthropic says its infrastructure footprint is roughly 200x smaller than the old Git-mirror setup.
  • There’s no public release, and none is planned for now.

The speed numbers are Anthropic’s own and haven’t been independently checked.

What Anthropic Scion actually is

Scion is a source control system, the same job Git does: tracking changes, history, and merges. It just makes very different design choices. Anthropic built it for one company’s extreme workload, not for everyone.

A seven-person team built Scion, a code review tool called Antique, and about six other systems in five months. By the end, the monorepo was fully migrated. Anthropic says Claude helped build the replacement for a bottleneck that Claude’s own output had helped create.

Why Git started to crack at 30,000 merges a day

When AI agents write code, people merge far more of it. Anthropic’s merges grew about twelvefold in four months. Its own summary says it well: “Every bottleneck we remove immediately leads to a further increase in the amount of code we produce.”

The old setup relied on hundreds of Git mirrors to serve all that traffic. Each mirror is a full copy that needs CPU, memory, and syncing. At that scale, keeping them all current became the problem.

If you’ve ever waited on a slow CI checkout, you’ve felt a small version of this. Anthropic just hit it at a scale most teams will never see.

How Scion differs from Git

Git assumes every developer holds a full copy of the repository. Scion drops that assumption and keeps the data on always-on servers that clients query when needed. That one change explains most of the differences below.

Area Git (typical setup) Scion
Local copy Full clone with history Fetches data on demand
History lookups Needs a local clone Queried through an API
Scaling Add more mirrors Independently scalable components
Works offline Yes No, it needs the server

The tradeoff is clear. You gain speed and scale, and you lose the offline freedom that made Git popular. Anthropic says CI and research jobs now check out code two orders of magnitude faster.

What the numbers prove, and what they don’t

The headline claims are big: about 200x less CPU and memory, and checkouts two orders of magnitude faster. They come from Anthropic’s own engineering post, and The New Stack notes it didn’t verify them independently. Treat them as strong claims, not settled benchmarks.

Anthropic also says Scion is “among the most well-tested and well-defended codebases we have ever worked on,” citing simulations, fuzzing, and rate limiting. That makes sense for a system every engineer depends on. A bug in source control can stall a whole company.

One more caution: the idea that other companies will hit the same wall is a forecast. Most teams merge nowhere near 30,000 times a day, and Git handles them fine.

Can you use Scion? Not anytime soon

No. Anthropic says Scion is “by no means a suitable replacement for git for general use.” It has no plans to release it, citing three reasons.

First, Anthropic’s token spending is far beyond what most businesses would want to pay. Second, Scion is too niche to help most teams. Third, other companies would face heavy migration work.

Anthropic does hope to work with GitHub, GitLab, and the open source community to bring some of Scion’s ideas into Git. If you want a taste of AI-assisted code workflows today, look at how GitHub Agentic Autofix handles code scanning alerts. And for a sense of how much code Claude can already produce, see the tsc-rs port of the TypeScript compiler.

Frequently Asked Questions

What is Anthropic Scion?

It’s Anthropic’s internal version control system. The company built it to replace Git in its monorepo after merges passed 30,000 a day.

Is Scion open source?

No. Anthropic has said it doesn’t plan to release Scion or build a public version soon.

Is Git going away?

No. Anthropic itself says Scion isn’t a general-purpose Git replacement, and Git remains the standard for almost every team.

Why did AI code cause the problem?

AI tools let people write and merge much more code, much faster. Anthropic’s merges rose from about 2,500 a day in May to over 30,000 in September.

My take: watch the ideas, not the product

You don’t need to change anything about your repo today. Scion matters as a warning sign: if AI agents keep multiplying merges, tools like CI, code review, and Git hosting will have to adapt. Keep an eye on whether GitHub and GitLab borrow any of these ideas, because that’s where this will actually reach you.


Comments

Leave a Reply

Your email address will not be published. Required fields are marked *