Confirmed 13 Oct 2026 · Labs A one-minute read

Anthropic threw out git and built its own, after daily merges grew 12 times.

Anthropic's monorepo left git for an in-house system called Scion in 5 months. Caveat: Scion is not released, and Anthropic says it is no replacement for git in general use.

Until now

Git is the floor every software company builds on, including the AI labs.

Now

Agent-written code can outgrow the industry's standard tool in 5 months.

Why it matters

Anthropic sells the coding agents that caused this. The volume it had to engineer around is the volume its customers are about to generate. 7 people rebuilt the foundation in 5 months; most companies have neither the people nor the warning. The bottleneck moves to whoever merges next.

Established

  • Anthropic published the migration on its own engineering blog on October 13.
  • Daily merges went from about 2,500 in May to over 30,000 in September.
  • A team of 7 built Scion and migrated the monorepo in 5 months.

Not established

  • That others need this. Anthropic calls Scion unsuitable for general use.
  • That agents wrote the 30,000 merges. Anthropic gives no split.
  • The 200x footprint saving. It is Anthropic's own internal measure.
The five-minute readThe record, the timeline, the weight and 4 sources

The record

Tuesday October 13, 2026 is the publication date on Anthropic's own engineering post, "Redesigning source control at Anthropic", read directly at anthropic.com. The framing is Anthropic's: "As our merges per day grew more than tenfold, source control became our biggest development bottleneck." The published numbers: about 2,500 code changes merged per day in May 2026, more than 30,000 per day in September 2026. The monorepo's main-branch history is almost 100 GB and a compressed working copy is over 25 GB. Anthropic performs about 25 million code checkouts per day for continuous integration, and estimates that fetching those naively would mean over 600 PB of git traffic per day. At peak it ran several hundred internal git mirrors, which became harder to operate as merge volume rose. The replacement is Scion, an in-house version control system; Anthropic says the monorepo was "fully migrated" from git in 5 months. Published results: Scion's infrastructure footprint is about 200 times smaller than the git mirroring it replaced, measured in CPU and memory; continuous integration and research checkouts run about 2 orders of magnitude faster, seconds instead of minutes; continuous integration alone gained 25% CPU capacity; each cache tier holds a hit rate above 99%. A team of 7 built Scion, a code review tool called Antique, code search, a source control identity system and about half a dozen related systems in the same period. One example given: a Claude Mythos Preview rewrite of the git-to-Scion ingestion pipeline used 20 times less memory and ran 4 times faster. Anthropic states that "Git assumes that clients work offline and need a complete copy of the repository" and that "Scion is by no means a suitable replacement for git for general use". On the engineers it writes: "Very often, we found that the role of the engineers was to tell Claude no." Not published: the share of merges a model wrote, any licence or release plan for Scion, the cost of the project, and any external benchmark.

How it got here

  1. Feb 5

    Anthropic publishes "Building a C compiler with a team of parallel Claudes" on the same engineering blog, an early public account of running many coding agents at once.

  2. May 2026

    About 2,500 code changes a day are merged into the monorepo. Several hundred internal git mirrors are running at peak, and the migration to Scion begins inside this window.

  3. Sep 2026

    Merges pass 30,000 a day, 12 times the May figure. Anthropic performs about 25 million checkouts a day for continuous integration.

  4. Oct 13

    Anthropic publishes the migration, the numbers and the design, says Scion is not a general replacement for git, and releases no code. It invites git platforms to take the ideas.

Who has to react

GitHub, GitLab and the git maintainers, whom Anthropic invites to take the ideas; Microsoft, which owns GitHub; every engineering organisation now shipping agent-written code; Anthropic's own customers, who buy the tool that created this volume; and the Linux kernel, whose creator published Claude-assisted memory management patches 2 days earlier.

What to watch

  • Would strengthen itA second company with more than 1,000 engineers publicly replaces or forks git, naming agent-generated change volume as the reason, by June 30, 2027.
  • Would weaken itAnthropic publishes a breakdown showing fewer than half its merges are model-written, or the git project ships always-online features Anthropic adopts, by December 31, 2027.
  • Would strengthen itAnthropic releases Scion under any licence, or markets it as a product, by December 31, 2027.

Why it weighs this much

Signal strength
CostMedium
CommitmentHigh
ReversibilityHard
PersistenceStructural

Cost is medium: 7 engineers for 5 months is a real bill but small for a company of Anthropic's size, and the work bought back 25% of continuous integration capacity. Commitment is high. The monorepo is fully migrated off git, published under the company's name, with the numbers attached. Reversibility is hard, because going back means re-mirroring a 100 GB history across several hundred mirrors to serve 25 million checkouts a day. Persistence is structural: source control is the floor every other tool stands on, and a company does not swap it twice.

The words

Monorepo
One repository holding all of a company's code, so every change is merged into the same history.
git
The version control system almost all software uses to record changes and merge work from many people.
Merge
Adding a finished change into the shared main copy of the code. Merges per day measures how fast code lands.
Continuous integration
Automated systems that check out the code and run tests on every change, which is why checkout speed matters.

Sources

Your call

Which explanation do you believe?

A call is final. Other people's calls show after yours.

8 contributions. Thank you.

You have built
a record here.

Keep it: create an account to verify your contributions and put your name to the answers you choose. Your record stays yours.

Keep my record ↗
Optional: help show whose perspectives are missing
Kept with your answers under a random id, never with your name. Used for one thing: showing you, on your record, where you stand next to people like you, once at least 20 of them have answered.

Add your signature

Stand behind your judgment.

Create an account to attach your name to this answer. Your other answers show no name unless you sign them too.

Sign up to add your name ↗

Already have an account?