SlotPricesCompare subscription prices
English
New: Your PDFelement Black Box Is Hiding Nothing. Here's the FixRead this first

Reading

Claude Outgrew Git. Anthropic's Scion Is a Warning to GitHub

Anthropic went from 2,500 merges a day to 30,000 and dropped Git for Scion, its own in-house tool. Should you switch too? No. Should GitHub worry? Yes.

Prices last read 2026-10-27

Short answer

Anthropic moved its main monorepo off Git and onto Scion, a source-control system it built itself, after daily merges rose from about 2,500 in May 2026 to more than 30,000 in September.In an engineering post dated October 13, 2026, Anthropic says a seven-person team finished the migration in five months. It reports that Scion's infrastructure needs about 200x less CPU and memory than its old Git mirroring setup, and that CI and research checkouts now take seconds instead of minutes. Anthropic is clear that Scion is not a general Git replacement and has not announced a public release. For almost every Claude user and developer, nothing changes today.

Source: Redesigning source control at Anthropic · 2026-10-27

What Anthropic actually announced

Anthropic's engineering blog describes a monorepo whose main-branch history is close to 100 GB, with a compressed working copy of more than 25 GB. Its CI runs about 25 million checkouts a day. Before Scion, the company relied on partial copies, repository snapshots and, at peak, several hundred internal Git mirrors to keep up. Merge volume grew roughly twelvefold in four months, and Anthropic credits Claude with writing much of that code.

Source: Redesigning source control at Anthropic · 2026-10-27; Anthropic replaces Git with custom source control system Scion (Crypto Briefing) · 2026-10-27

A panicking messy-haired person braces an overflowing funnel beside a custom cart.
Anthropic built a new source-control system when its merge volume overwhelmed Git.

Git's design is decentralized: every clone holds the whole repository and can work offline. Scion makes the opposite bet. It is server-centric and assumes its clients, mostly agents and automated jobs, are always online. The server handles history, blame, commits, merges and rebases, and clients fetch only the data they need through sparse or virtualized checkouts. The post says Scion avoids packfiles, keeps refs to a minimum and needs no repository maintenance. Its client is called scn. The same team also built Antique, a code-review tool.

Source: Redesigning source control at Anthropic · 2026-10-27

Anthropic gives these results: an infrastructure footprint 200x smaller in CPU and memory than its previous Git mirroring, CI and research checkouts two orders of magnitude faster, and a 25% gain in CI CPU capacity. Claude also helped build the system itself. According to the post, an early version of Claude Mythos Preview rewrote the Git-to-Scion ingestion pipeline to use 20x less memory and run 4x faster. Humans are still involved: engineers review every change request, but Anthropic says they now examine the intent of each change instead of reading every line.

Source: Redesigning source control at Anthropic · 2026-10-27; Anthropic replaces Git with custom source control system Scion (Crypto Briefing) · 2026-10-27

Scion is by no means a suitable replacement for git for general use.

Anthropic engineering blog, "Redesigning source control at Anthropic" (Oct 13, 2026)

Source: Redesigning source control at Anthropic · 2026-10-27

That line is the main thing to take away if you were wondering whether to switch. Anthropic says Scion's ideas only pay off for very large monorepos or heavy agent workloads, and that its internal parts are too bespoke to package in a broadly useful form. The company says it is sharing the design so it can partner with GitHub, GitLab and the open-source community, and it suggests Git platforms could borrow pieces such as server-side RPCs without abandoning Git's model.

Source: Redesigning source control at Anthropic · 2026-10-27

A cautious messy-haired person compares a standard toolbox with an enormous custom wrench.
Most teams should keep Git, but GitHub must address the scaling limits Anthropic exposed.

Who is affected, and what to do

Where you stand

  • Claude or Claude Code subscriber: no change. Scion is Anthropic's internal infrastructure, not a product feature.
  • Developer on a normal-sized repo: keep using Git. Anthropic itself says Scion is not meant for general use.
  • Platform team running a huge monorepo with many coding agents: read the post for the design ideas (server-side operations, sparse checkouts, fewer refs). There is no Scion to download.
  • Searching for it: there is a separate, unrelated Google project also called Scion, so check which one an article means.

Source: Redesigning source control at Anthropic · 2026-10-27; Anthropic replaces Git with custom source control system Scion (Crypto Briefing) · 2026-10-27

The take: the bottleneck isn't the model anymore

The most important line in Anthropic's post isn't the 200x figure. It's the opening claim that coding is no longer the bottleneck. For years, the debate about AI coding has been about whether the model can write good code. This post skips past that question. The model writes so much code that the plumbing around it — source control, CI, review — is now the bottleneck. Git was designed for humans who commit a few times a day and sometimes work on a plane. Agents never go offline and never stop committing. That isn't Git failing. Git is succeeding at a job nobody is giving it anymore.

Overrated: the idea that you should switch to anything like this. Your startup's 2 GB repo is fine, and copying a bespoke system built by a seven-person team at an AI lab would be cargo-cult engineering. Underrated: what this means for GitHub and GitLab. If agent-heavy teams keep growing, forges built around offline full clones and a human-paced pull-request flow will feel the same strain Anthropic did, only later. Anthropic chose to publish a blueprint instead of a product. That's polite, but it also tells the forges that the biggest customers of the agent era will build their own tools if nobody else does. One part should bother everyone: humans now review intent, not lines. That may be the only workable approach at 30,000 merges a day, but it is a real change in who is accountable for code.

Tip

If your team is starting to feel this pain with Claude Code or other agents, look at CI checkout times and mirror sprawl first. Those are the costs Anthropic says Scion removed, and partial or sparse checkouts in your current Git setup may get you part of the way there.

Optional: compare Claude subscription listings (a third-party seller listing, not official Anthropic access or an endorsement). That link carries our partner code Sk52g, which is how a purchase is attributed to this site. Promotion code UPD3S.

Before you pay

Check the price before you renew

Every price dated, every source linked.

See it on GamsGoAffiliate link · Promotion code UPD3S.
  • Dated pricesRead from the seller and dated.
  • Terms firstSeller notes and service terms are linked.
  • No extra costCommission never changes the price you pay.