You've scaled your agents. Great.
Agents now commit and merge around the clock, and git was built for humans. Why agent first source control is coming sooner than most teams expect.
But I bet you didn't know they're working overtime. Committing code. Merging code. All day, every day.
Here's what's coming, and it's worth being ready for: new infrastructure that sits outside the dev stack you already run. Hardly anyone expected to need it this soon.
Agent-first source control is becoming a thing.
Git was built for humans. Local copies, offline work, human pace. Agents are the opposite: thousands of them, always online, merging constantly. Anthropic called it infrastructure built for human, rather than agent, scale.
The numbers moved fast. Anthropic went from 2,500 merges a day in May to more than 30,000 a day in September, with 25 million checkouts a day. GitHub pushes jumped from 0.69 billion to 3.35 billion a month, with 7.38 billion commits in September alone.
Four big players, four different bets.
Anthropic replaced git itself with Scion, an internal system.
Cursor replaced the host with Origin, and kept git.
GitHub is rebuilding underneath on Azure storage, for up to 35 times the write throughput.
GitLab has a private beta where agents query the server instead of cloning.
Different answers to the same question.
So what do you do? Name it first: agent-first source control is a category your stack doesn't have yet. Then factor it into your plans now, before your merge queue forces the issue. And if agents are committing code nobody governs, that's a security and compliance hole, not a tooling preference.
Your agents won't wait for your roadmap.