Artificial Intelligence
Anthropic details Scion monorepo version-control system
Anthropic said it moved its monorepo from git to Scion, an in-house version-control system, after daily code merges rose from about 2,500 in May 2026 to more than 30,000 by September.
- Anthropic said Claude had become able to iterate on research loops, optimise complex programs and build new services, leaving source control, builds and continuous integration as the main bottlenecks.
- The company said its daily merge count rose from about 2,500 in May 2026 to more than 30,000 in September.
- Anthropic said it built Scion and moved its monorepo from git in five months.
- The article said Scion used online clients, server-side commits and merges, changesets and derived data, with horizontally scalable servers and no fully materialised repository copy on the server.
Anthropic said Claude had changed what limited its engineering work, because the model could carry out research loops, tune programs and build new services. The company said that left source control, build systems and continuous integration as the main constraints.
It said merge volume increased from roughly 2,500 code changes per day in May 2026 to more than 30,000 a day by September. Anthropic also said it expected that pace to continue and that the demand for merges was not likely to ease soon.
To cope with that load, Anthropic said it built Scion and moved its monorepo off git in five months. In the same period, it also shipped Antique, code search, a source-control access-control system and other tools for handling reviewed code.
Anthropic said its own workload was unusual because it relied on Claude for software work more than most companies. It said other users of AI coding tools would probably encounter similar limits later, which was why it chose to describe what it had built and learned.
The article described Scion as a system designed for clients that stayed online, with the server handling commits, merges and rebases. It said the architecture used changesets, derived data and content-addressed storage, and that the scn client and scion-daemon handled object access across nodes.
Named in this story
Companies
- Anthropic
- published the account and said it migrated its monorepo from git
Products and systems
- Claude
- Anthropic’s model that drove the higher coding and merge volume
- Scion
- Anthropic’s in-house version control system for the monorepo
- Antique
- the code review surface Anthropic built alongside Scion
- git
- the source control system Anthropic replaced for its monorepo
- Piper
- Google’s source control system cited as prior art
- Sapling
- Meta’s source control system cited as prior art
- Spanner
- the database used for a ref update and for writing derived results
- scn client
- the Scion client that fetched trees and blobs from the server
- scion-daemon
- the per-node daemon that stored shared repository objects
How the source tells it
Self-authored technical case study with clear promotional framing around Claude, Anthropic’s scale, and the need for a new source-control system.
- vendor boosterism the company’s own claims about Claude’s speed and Anthropic’s unusual scale are repeated as the basis for the piece
- urgency rapid growth figures and warnings that the pressure points would not ease soon drive the narrative
- speculation presented as forecast a hedged prediction about other organisations facing the same problems is offered as a near-term expectation