Redesigning source control at Anthropic

    We’re completely rethinking our priors. This project prompted us to take a very hard look at other workflows designed for human scale. A proper merge queue, for example, doesn’t make much sense at agent scale. What does CI even mean when hundreds or even thousands of changes can merge while tests are running? We haven’t been able to effectively replicate the industry standard of a global repository lock on the merge queue, so instead, we’ve invested in post-merge and pre-deploy automated testing. This does mean that concurrent changes can conflict, but Claude can typically fix these conflicts faster than humans can even identify them.

[dead]

[dead]

[dead]

[dead]

[flagged]

[dead]

tl;dr why is it better than git?

Source control for huge monorepos has prior art, notably Google’s Piper and Meta’s Sapling, so we were able to build Scion with their hard-won lessons in mind.

What an unexpected candor! Of course you plagiarize prior art.

No sane person is going to put their sources in this slopware Scion monster.

> Git offers tools for working with a slice of a repository, such as shallow clones, sparse checkouts, and promisor remotes.

I honestly just cannot. Just tell me what the workflow is. Give me a video that is Twilio-level simple explanation.

Back to SVN then? Noted.

Oh wow. There is nothing I'd rather use less than version control vibe coded by Anthropic.