AnswersPublished19 sources
Why Anthropic Built Scion After Git Hit a 30,000-Merge-a-Day Bottleneck
Anthropic moved its monorepo to Scion after daily merges rose from about 2,500 in May to more than 30,000 in September. Scion keeps clients lightweight: servers handle operations such as commits, merges and history queries, while clients request needed data rather than maintaining full repository copies.
Published byEdited with GPT-6 LunaImages generated with GPT Image 2
Research answer
Key takeaways
- Anthropic moved its monorepo to Scion after daily merges rose from about 2,500 in May to more than 30,000 in September.
- Scion keeps clients lightweight: servers handle operations such as commits, merges and history queries, while clients request needed data rather than maintaining full repository copies.
AI Prompt
openai.comCreate a landscape editorial hero image for this Studio Global article: Why did Anthropic replace Git with its in-house version control system Scion, as described in its October 13, 2026 engineering post, and how. Article summary: Anthropic replaced Git for its monorepo because AI-generated changes overwhelmed infrastructure designed around human development: daily merges increased from roughly 2,500 in May to more than 30,000 in September, making. Topic tags: general, general web, user generated. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fa
Anthropic replaced Git in its monorepo after daily merged code changes climbed from about 2,500 in May to more than 30,000 in September 2026, making source control its biggest development bottleneck. The company says it built Scion and migrated the monorepo in five months. 8
9
Why Anthropic changed its source-control setup
The issue was not simply that the repository was large. Anthropic described a combination of rapid merge growth and heavy checkout demand: its main-branch history was close to 100 GB, a compressed working copy exceeded 25 GB, and continuous integration (CI) performed around 25 million code checkouts a day. 9
That workload made a Git-based setup with extensive repository copies and mirrors costly to operate at Anthropic’s scale. The company has described demand for merging code as “practically infinite”: removing one bottleneck can allow even more code production, so infrastructure may need to keep scaling rather than settle at a fixed workload. 29
How Scion works differently
Scion is designed around clients that can reach a server. Rather than requiring each client to do every source-control operation locally, the system provides server-side operations and APIs. The server handles tasks such as commits, merges, rebases and history lookups; clients keep a bounded cache and fetch the data they need. 2
4
This changes the trade-off. Git’s distributed model gives users a local repository, while Scion’s approach relies more heavily on shared infrastructure and connectivity. Anthropic’s design suits its reported workload of automated jobs and agents, but that does not make it the right choice for every developer or project. 2
7
What Anthropic says the migration achieved
Anthropic reported that Scion’s CPU-and-memory footprint was about 200 times smaller than its previous Git-mirroring infrastructure. It also reported that checkouts that had taken minutes could take seconds, freeing 25% of CI CPU capacity. These are company-reported results, not independently reproduced benchmarks. 4
10
The migration also involved more than version control. Anthropic says it built a code-review surface called Antique, code search, access-control tooling and other systems for handling and landing reviewed changes. A seven-person team worked on Scion and Antique as the monorepo migration took place. 3
8
A specialized response, not the end of Git
Anthropic’s account supports a narrower conclusion than “Git is obsolete.” Scion was built for a particularly large, fast-moving internal monorepo and for clients that can rely on server access. Reports describe it as an internal system, not a general-purpose Git replacement. 5
7
The broader lesson is about matching source-control architecture to development patterns: when repository size, checkout frequency and merge volume grow together, moving more work to shared services can be one way to address the resulting infrastructure pressure.
Studio Global AI
Continue your research
This page includes a source-backed answer you can continue inside Studio Global.
People also ask
What is the short answer to "Why Anthropic Built Scion After Git Hit a 30,000-Merge-a-Day Bottleneck"?
Anthropic moved its monorepo to Scion after daily merges rose from about 2,500 in May to more than 30,000 in September.
What are the key points to validate first?
Anthropic moved its monorepo to Scion after daily merges rose from about 2,500 in May to more than 30,000 in September. Scion keeps clients lightweight: servers handle operations such as commits, merges and history queries, while clients request needed data rather than maintaining full repository copies.