Anthropic Details Scion, a Source-Control System Built for 30,000 Daily Merges

·1 views

Anthropic has published the design of Scion, a source-control system it built after autonomous agents pushed its monorepo past 30,000 merges a day by September 2026. Daily merges had risen roughly twelvefold from May, and the company found that developer infrastructure designed for human scale had become the main constraint. Git's distributed model proved a poor fit because its workarounds, including hundreds of internal mirrors, kept decaying and its offline-first design was unnecessary for always-connected agents and CI jobs. Scion instead centralizes history, commits, merges, and blame on one authoritative server, keeps clients thin, and records commits as append-only changesets. Anthropic says Scion is not meant as a general git replacement, though it expects the underlying approach to influence other projects.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Three Worktree Managers Compared for Running Parallel Coding Agents

A small set of tools now helps developers stop coding agents from overwriting each other's files when they run in one repository. Claude Squad, Conductor and Hermes IDE all rely on git worktrees, giving each agent its own folder and branch. The article notes that the core workflow is similar across them, with the main differences being which agents they support, their operating system support, and how they handle setup and review. Claude Squad is a terminal app built on tmux and worktrees, while the article's author, who builds Hermes IDE, says they have not personally run Conductor or Claude Squad.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Buckle Lets AI Agents Work on Remote Machines Without Full SSH Access

Buckle is a remote execution harness that runs on a user's machines and gives AI agents scoped access to an environment such as a container, remote server, or laptop. Agents connect over HTTP or stdio and use only the tools and approval rules the user configures, including file access, a sandboxed shell, web fetch, a browser, and Git. Every action is allowed, requires approval, or is denied before it runs, with deny rules taking precedence. Users can restrict commands by pattern, limit network access to an approved host list, and share folders read-only, while credential files always prompt for approval. The project is part of a broader effort, 5straps, aimed at auditable agent networks for enterprises, and early access is currently open for feedback.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Local Voters Push Back on Meta's AI Data Center Plans After Midterm Ballot Measures

Meta president Dina Powell McCormick said the midterm election results will make building data centers significantly harder for the company. Voters decided more than 40 ballot measures on data centers across ten states, and opponents won nearly all of them, including a capacity cap in Trenton, Ohio that passed with almost 80 percent of the vote. Local opposition has risen sharply, with one estimate putting the share of people opposed at 75 percent, up from 42 percent a year earlier. Analysts at New Street Research estimate local resistance blocked or delayed nearly $200 billion in data center projects in the first half of 2026. Meta has proposed a model in which it covers its own electricity costs, directs tax surpluses to local schools and first responders, and hires locally, but critics question whether this approach can win community support at scale.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Missing APX Field in APC Projects Means Status Is Unknown, Not Installed

A project's .apc/project.json may include an apx field, and its absence or a null value means the project has not declared its APX status rather than confirming installation. The article argues that treating unknown as installed leads to brittle automation, while treating it as declined could hide useful local tooling. An explicit value of installed signals that APX is available for the project, whereas declined signals a deliberate choice to avoid suggesting or running APX there. When the field is missing, the recommended approach is a local availability check only when APX would help the current task. Because APX is installed per machine and project metadata travels with Git, maintainers should set the field deliberately rather than assume it.

0 comments Read more at DEV Community