TITLE: Anthropic Replaced Git After Claude Caused a 12x Surge in Daily Code Merges DATE: 2026-10-14 COMPANY: Anthropic TOPIC: AI Infrastructure SUMMARY: Anthropic built a custom version control system called Scion after Claude-generated code pushed daily merges from 2,500 to more than 30,000 in four months. A seven-person team completed the migration off Git in five months. The announcement is a concrete signal of what AI-at-scale does to developer infrastructure. WHAT CHANGED: Anthropic published an engineering post on October 13, 2026 explaining why and how it replaced Git as its internal version control system. The driver was volume. Claude had taken over a significant share of Anthropic's internal code writing, and the resulting pace of merges exposed the limits of Git at that scale. By September, the team was processing more than 30,000 merges a day, up from around 2,500 in May. The fundamental problem was architectural. Git was designed around the assumption that humans write code, which means commits arrive at a pace and frequency that client-server architecture can absorb. When AI agents take over code generation, that assumption breaks. Clients generating and pushing code at agent speed create a communication and synchronisation overhead that grows faster than the underlying hardware can absorb. Scion addresses this with two key changes. First, commits are processed server-side rather than client-side, removing the round-trip cost of traditional Git push operations. Second, Scion uses changesets rather than the commit-based model Git uses, which simplifies branching and merging when many agents are working on overlapping parts of the codebase simultaneously. The result is a 200x reduction in CPU and memory footprint compared to Anthropic's previous mirroring infrastructure. Anthropic was explicit that Scion is not intended for general use. The team stated it will not be open-sourced and that the design is specific to Anthropic's monorepo environment. What Anthropic is sharing is the design thinking: server-side commits, on-demand fetching, and changeset-based modelling are ideas that could improve Git's performance at scale if the broader community adopted compatible changes to server-side protocols and negotiation. WHY IT MATTERS: The Git problem is coming for every serious AI team. If you are deploying AI coding agents at any meaningful scale, Git was not designed for what you are asking it to do. The constraint Anthropic hit at 30,000 merges a day is a version of the constraint your team will hit at 3,000 or 300. The threshold differs; the pattern does not. This is the most concrete evidence yet that AI agents have crossed from assistant to primary contributor. Scion was not built because Claude occasionally writes code. It was built because Claude writes most of Anthropic's code. That shift is no longer theoretical at the leading AI labs. The question for engineering leaders is when it arrives in their own organisations, not whether. Developer toolchain investment is now an AI strategy decision. Until now, most discussions of AI adoption focused on the AI layer: which model, which agent framework, which deployment platform. Scion shows that the toolchain one level below the AI layer matters just as much. Companies that scale AI coding agents without adjusting their underlying infrastructure will hit the same wall Anthropic hit. The 200x efficiency gain is a signal about the scale of the problem. A 200x reduction in CPU and memory footprint is not an incremental improvement. It indicates that the old infrastructure was genuinely unsuited to the new load, not merely inefficient. Any organisation that finds its existing tooling degrading at this rate needs to treat that as an architectural problem, not a capacity problem. The seven-person, five-month timeline is a benchmark for AI infrastructure teams. A small team rebuilt core infrastructure for one of the world's most demanding engineering environments in under half a year. That is achievable because the team had both a clear problem statement and AI assistance to accelerate the build. Organisations that have not yet invested in dedicated AI infrastructure teams should register this timeline as evidence that the investment pays back quickly. DAVID & GOLIATH ANALYSIS: The Scion announcement matters more as a precedent than as a product. Anthropic is not sharing the code, and the specific engineering choices it made are tightly coupled to its own monorepo setup. What it is sharing is confirmation that the infrastructure gap between human-paced development and AI-paced development is real, large, and solvable with focused effort. For operators running 10-to-200-person teams, the immediate takeaway is not to rebuild version control. It is to take seriously the idea that AI coding agents will change the shape of your development pipeline faster than you expect, and that the places where that change shows up first are not always the obvious ones. At Anthropic, the bottleneck was not compute, was not the model, and was not the product roadmap. It was Git. The deeper implication is about how AI system value accumulates inside an organisation. Anthropic's ability to move fast was not limited by the quality of Claude. It was limited by the infrastructure surrounding Claude. Teams that invest in clearing those infrastructure bottlenecks compound their advantage over time, because each cleared constraint allows the AI layer to deliver more value. That logic applies to the 10-person team using AI coding tools as much as it applies to Anthropic's engineering organisation. RELEVANT SYSTEMS: Employee Amplification Systems, AI Growth Engine SOURCE URL: https://davidandgoliath.ai/daily-ai-briefing/anthropic-scion-git-replacement-ai-code-volume FEED URL: https://davidandgoliath.ai/daily-ai-briefing/feed --- Published by David & Goliath | https://davidandgoliath.ai Daily AI Briefing: one AI development per day, decoded for business operators. This is a structured companion file optimised for LLM retrieval and citation.