Skip to content
Industry Hub
← Industry News

GitHub is adding 4 million cores as AI agents flood the platform

September brought 7.4 billion commits, and more than 40 percent of pull requests were opened by agents. GitHub is rebuilding capacity to stay up.

Industry Insights 2 min read
  • #GitHub
  • #infrastructure
  • #agents
  • #Octoverse

The other Universe story is not a feature. It is load. GitHub said the platform recorded about 7.4 billion commits in September 2026, roughly five times September 2025. In the twelve months through September it logged 34.3 billion commits, about triple the prior year.

Agents are a large share of that traffic. More than 40 percent of pull requests in September were opened by AI agents, up from 17 percent in March. A lot of the new volume is new repositories, often created for agent-driven projects rather than for a human sitting in an editor.

The capacity response

To absorb that, GitHub is bringing online about 4 million additional CPU cores and 160 petabytes of high-speed storage this year, mostly in Microsoft Azure, after already adding on the order of 3 million cores earlier in 2026. It is also separating compute from storage. The stated goal is much higher write throughput — GitHub has talked about up to 35 times — and a multi-region Azure footprint after a run of reliability problems.

This is the unglamorous side of the agent era. An agent does not wait for office hours. It opens a repository, pushes, opens a pull request, and kicks CI on a loop. The platform has to treat that as the baseline, not a spike.

What it means if you ship on GitHub

If your CI bill or your queue time jumped this year, you are not imagining it. Agent traffic is now a platform-scale workload, not a Copilot sidebar.

Three practical checks:

  1. Rate-limit agent jobs. Unbounded retry loops are how a single agent becomes an outage for everyone else on the account.
  2. Separate agent identities. A pull request opened by an agent should be obvious in review, and its token should not be a human’s personal credential.
  3. Watch write-heavy workflows. The bottleneck GitHub is redesigning around is write throughput. Monorepo bots that rewrite the same files all day will feel that first.

GitHub’s developer base is now reported above 225 million accounts. The growth that matters for operators is not the account count. It is that a rising share of the work on those accounts is no longer typed by a person.

Sources