On Oct 13 Anthropic's engineering blog said merges grew from about 2,500 per day in May 2026 to more than 30,000 in September, making human-scale git infrastructure its biggest bottleneck. A seven-person team built Scion, an always-online version control system, plus the Antique code-review tool, and fully migrated the monorepo off git in five months. Scion's footprint is 200x smaller in CPU and memory than the old git mirrors, CI checkouts went from minutes to seconds, and CI gained 25% CPU capacity. Scion is not being open-sourced; Anthropic wants to work with GitHub, GitLab and the OSS community to bring the ideas to git.

Key Takeaways

  • ✓Scale: ~2,500 merges/day in May vs 30,000+ in September; main history near 100 GB, compressed working copy over 25 GB, ~25M CI checkouts per day (600+ PB/day if fetched naively with git)
  • ✓Design: always-online clients, server-side blame/history/commit/merge/rebase, content-addressed data in Spanner and blob storage, no packfiles or repo maintenance
  • ✓Results: 200x smaller CPU/memory footprint than the git mirrors, 99%+ cache hit rate per tier, checkouts two orders of magnitude faster, 25% CI CPU freed
  • ✓Team: seven engineers built Scion, Antique and related systems in five months; an early Claude Mythos Preview rewrite of the ingestion pipeline used 20x less memory and ran 4x faster
  • ✓Process: no global-lock merge queue, replaced by post-merge and pre-deploy testing; Scion stays internal, with ideas offered to GitHub, GitLab and OSS git
Anthropic replaces git with in-house Scion: daily merges grew from ~2,500 to 30,000+, and a 7-person team migrated the monorepo in five months
🖼️Official Media
Click to view high-res
🧭

Heavy Claude Code use: compare subscription limits and API bills

Compare 40 dev plans & simulate token costs vs $20/mo subscriptions

🔬

In-Depth Technical Analysis

Anthropic's Oct 13 engineering post explains why it left git for an in-house system. Merges to its monorepo rose from about 2,500 per day in May 2026 to more than 30,000 in September; main-branch history is nearly 100 GB and CI performs roughly 25 million checkouts a day, which would be 600+ PB of git traffic if fetched naively. Shallow clones, sparse checkouts and several hundred internal git mirrors were no longer enough.

Scion assumes clients (mostly agents and jobs) are always online. The server handles history, blame, commits, merges and rebases; clients keep a bounded cache and use sparse or virtualized checkouts. Commits are server-side changesets in a write-ahead log that list changed files with content-addressed pointers, backed by Spanner and blob storage, with no packfiles and no repo maintenance. A daemon, regional cache and server tier all speak the same RPCs and each keeps a 99%+ hit rate. The design borrows lessons from Google's Piper and Meta's Sapling.

Anthropic reports a 200x smaller CPU and memory footprint than its git mirrors, checkouts two orders of magnitude faster, and a 25% CI CPU win. Seven engineers built Scion, the Antique review tool and related systems in five months; an early Claude Mythos Preview rewrite of the ingestion pipeline used 20x less memory and ran 4x faster. Scion will not be released, but Anthropic suggests git forges add server-side RPCs and better-composed sparse features, and says it wants to work with GitHub, GitLab and the OSS community. These figures are self-reported.

Action HubReady to adopt this in production?

Benchmark side-by-side against alternatives, or calculate monthly token cost vs subscription break-even.

Up NextClaude Code Projects opens to every Pro and Max user on the waitlist: one conversation coordinating parallel cloud threads
Read Now→