For almost two decades, "where does the code live?" had one boring answer: GitHub.
In 2026 that answer stopped being boring. In the space of a few months:
- Cursor (now owned by SpaceX) launched Origin, an agent-first Git host built into the editor.
- OpenAI built Pando, its own Git backend, and is acquiring Pierre Computer to put Git hosting directly inside Codex.
- Anthropic went further and replaced Git entirely for its monorepo with an in-house system called Scion.
This post covers why this is happening, why GitHub has been struggling, and what each of these tools actually does differently.
TL;DR
- AI agents produce code at a volume Git hosting was never designed for. Anthropic went from ~2,500 merges/day to 30,000+ in four months. OpenAI's monorepo commits grew 2,442% from Q1 2024 to Q4 2026.
- GitHub buckled under that load. One independent tracker counted 257 incidents (48 major) between May 2025 and April 2026, and big outages kept happening through November.
- Big AI labs can't have their whole engineering org blocked when GitHub goes down, so they're building their own infrastructure.
- Cursor Origin is the only one you can actually use today. OpenAI's Code Storage is coming to Codex. Anthropic's Scion is internal-only.
- GitHub isn't dead. It's mid-migration to Azure, has added huge capacity, and still has the network effect nobody else has.
Part 1: GitHub's rough 2026
Let's start with the uncomfortable part.
The numbers
- An independent monitoring service recorded 257 incidents, 48 of them major outages, from May 2025 to April 2026. February 2026 was the worst month, with 37 incidents.
- GitHub's own incident history listed 26 incidents in April and 23 in May (its monthly availability reports count fewer, because they only include incidents that degraded performance).
- One analysis of a 30-day window (May 27 to June 26) counted 25 incidents, nearly one per day, though many were narrow and short.
Some of the worst hits
| Date | What broke |
|---|---|
| Mar 2026 | Datastore auth issues pushed Copilot Coding Agent error rates to 100%, twice |
| Apr 1 | Code search fully unavailable for 2h20m; 100% of queries failed |
| Apr 23 | A merge-queue bug produced incorrect squash merges when groups contained multiple PRs |
| May 2026 | GitHub Actions: in one window, all newly queued runs failed to start |
| Jun 8 | ~17% of unauthenticated requests got 504s (peaking at ~34%) due to abusive automated traffic |
| Aug 17 | Major outage; Copilot services took the longest to recover |
| Oct 29 | An Azure network disruption hit all three Central US availability zones and 34,128+ signed-in users |
| Nov 3 | Git operations over HTTPS degraded for ~7.5 hours |
| Nov 10 & 16 | Repo pages, PRs and Actions degraded; a 4h27m pull request incident on Nov 16 |
In GitHub's own October report, the company admitted reliability was still not where it needed to be.
The moment it became personal
On April 28, 2026, Mitchell Hashimoto (HashiCorp co-founder, creator of Vagrant, Terraform and Ghostty, and GitHub user #1299) announced that Ghostty is leaving GitHub. He had kept a journal marking every day a GitHub outage blocked his work; one tally put his experienced uptime at about 90%, well below GitHub's 99.9% SLA. His verdict, as reported by The Register: GitHub is "no longer a place for serious work."
Zig, Strudel and Tenacity have also moved off GitHub over 2025–2026.
Part 2: Why is GitHub failing? (It's the agents.)
GitHub didn't get worse at engineering overnight. The workload changed underneath it.
Agent-scale traffic
- New repositories per month jumped from 10 million (first hit in 2025) to 30.3 million per month in 2026.
- GitHub Actions jobs reached roughly 45 billion in 2026.
- At Ignite last week, Satya Nadella said agents are driving exponential growth in GitHub pushes, commits and PRs, and that Microsoft is rebuilding GitHub's core to keep up.
- An academic paper on the decline frames AI load as the trigger, not the root cause: the load exposed architectural weaknesses that were already there.
Why Git and GitHub's architecture struggle
- Git was designed for humans working offline. Every clone carries the full history; coordination happens at push time. That's great for a few hundred engineers, terrible for thousands of always-online agents doing tiny pushes all day.
- Ref updates become the bottleneck. When thousands of writers push to different branches, replicated Git hosts spend a lot of effort coordinating ref updates across replicas. OpenAI concluded every existing strategy for this cost too much once agents arrived.
- Shared databases. GitHub's own reports describe shared datastores (like its oldest database,
mysql1) whose problems cascade into PRs, Issues, Actions and Copilot all at once. - Half-migrated infrastructure. GitHub is moving from its own datacenters to Azure. In July, the Actions component that bridges the monolith to Actions was still in GitHub's own datacenters and became a capacity bottleneck. In October, an Azure network disruption then took down Central US.
Why the labs can't just wait
For OpenAI and Anthropic, coding is the product. When GitHub goes down, their engineers and their agents stop. The Information reported that a rise in GitHub disruptions is what pushed OpenAI to start building an alternative. And with the commit numbers above, even a perfectly healthy GitHub would struggle with that load.
There's also a strategic angle: GitHub is owned by Microsoft, and Microsoft's GitHub Copilot competes directly with Cursor, Codex and Claude Code. Owning your own code layer means owning the data, workflows and integrations around your agents.
Part 3: The new contenders
🚀 Cursor Origin (Cursor / SpaceXAI)
Background: SpaceX announced its acquisition of Anysphere, Cursor's maker, on June 16, 2026 and closed it on August 14 for $60 billion in stock, folding Cursor into a new SpaceXAI division. Origin shipped three days later, on August 17, the same day GitHub had a major outage.
// Detect dark theme var iframe = document.getElementById('tweet-2067012220832329782-860'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2067012220832329782&theme=dark" }
// Detect dark theme var iframe = document.getElementById('tweet-2089399057659596847-287'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2089399057659596847&theme=dark" }
What it is: a Git-compatible forge that lives in a new Codebase tab inside the Cursor app. Cursor calls it "agent-native infrastructure."
What it does today:
- Standard Git: push/pull, branches, code browsing, code search.
- Full pull request workflow: timeline, commits, checks, diffs, comments, merge.
- Two-way GitHub sync within seconds, so you can run both. For repos that started on GitHub, GitHub stays the source of truth.
- Direct access for Cursor agents, with an API and MCP for extensibility.
- Agent-assisted merge conflict and CI-failure resolution.
- Integrations: launched with Vercel, Depot and Buildkite, and by October had 20+ integrations and a public app marketplace.
// Detect dark theme var iframe = document.getElementById('tweet-2110075611633074295-248'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2110075611633074295&theme=dark" }
How it's better than GitHub (for agent workflows):
- Speed for agents. Early-preview reports cited figures like ~296,000 clones per hour, sub-400ms global sync, and cloud agents starting about 3x faster on longer tasks because their environments are ready to go.
- No context switching. Repo, PR review and agent all live in the editor.
- Built for agent-written code. Cursor says it's working on helping reviewers understand agent-written code without reading every line, and on automatically getting PRs to a mergeable state.
- Not tied to the Microsoft stack. For teams wary of the VS Code / Copilot / Azure ecosystem, that's a selling point.
Caveats:
- Early beta, paid plans only, and repositories are private to Cursor team members.
- It was rolled out opt-out by default (Enterprise admins could opt out).
- Code custody: after the SpaceX acquisition, critics flagged that Cursor's privacy documentation doesn't clearly say how code stored on Origin is governed.
- Analysts generally call it a credible alternative for repo hosting and PRs, but not yet a replacement for the wider GitHub platform (Actions, Packages, Issues, community).
The community saw it coming:
// Detect dark theme var iframe = document.getElementById('tweet-2066950461790536156-210'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2066950461790536156&theme=dark" }
// Detect dark theme var iframe = document.getElementById('tweet-2066928345246470204-779'); if (document.body.className.includes('dark-theme')) { iframe.src = "https://platform.twitter.com/embed/Tweet.html?id=2066928345246470204&theme=dark" }
🧠 OpenAI: Pando + Code Storage → Codex
OpenAI is attacking the problem at two layers.
1. Pando (internal Git backend, Nov 2, 2026)
- A new Git-compatible backend written in Rust that now powers all development in OpenAI's monorepo, rolled out without interrupting work or changing how engineers use Git.
- Built in about 10 weeks after Codex-driven development overwhelmed the old systems.
- Median push latency cut by ~80% (nearly 5x), merge reliability improved to 99.99% (it had sometimes dropped below 90%), and it serves close to a petabyte of Git data per day.
- Key design idea: it coordinates updates to each branch independently, so many writers on different branches don't block each other, and it optimizes for many readers fetching the same history.
- Unlike Anthropic, OpenAI kept Git and is contributing improvements upstream (its Git fork is at
github.com/openai/git).
2. Pierre Computer acquisition (Nov 4, 2026)
- OpenAI is acquiring Pierre Computer Company, a roughly ten-person startup behind Code Storage: Git-based hosting with API ergonomics designed for machines.
- Pierre's open-source Trees and Diffs libraries already power file browsing and diff review in the Codex app.
- OpenAI plans to bring Code Storage fully into Codex, so your code can live where your agent works. Existing customers can keep using Code Storage until then, and the open-source projects stay open.
What it improves: parallel agentic Git workflows at huge scale, and an end-to-end "generate → store → review → merge" loop inside Codex. Earlier in the year, The Information reported OpenAI had even considered selling its code repository product to customers.
🌱 Anthropic: Scion (replacing Git itself)
Anthropic went the furthest.
- On October 13, 2026, Anthropic published Redesigning source control at Anthropic. Daily merged changes in its monorepo rose from about 2,500 in May to more than 30,000 in September, and source control became its biggest development bottleneck.
- Its framing: coding is no longer the bottleneck; the developer infrastructure built for human scale is.
- So it built Scion, an in-house version control system, and fully migrated the monorepo off Git in five months with a seven-person team.
How Scion is different from Git:
- Client-server instead of distributed. There's one central source of truth; clients ask for what they need instead of carrying a full copy.
- Heavy operations run on the server: commits, merges, rebases, history and blame queries.
- No packfiles. Data is stored distributed on the server side.
- API-based source control, so a CI job or tool can query code history directly.
- Anthropic credits Meta's Mononoke and its Bonsai data model for pioneering many of these techniques. The Register compared the approach to Subversion, and Google has long done something similar with Piper.
Reported results (Anthropic's own measurements):
- ~200x less CPU and memory than the old Git mirroring infrastructure.
- Checkouts in seconds instead of minutes, about 25 million checkouts per day.
- 25% of CI compute capacity freed up.
- A companion code review tool called Antique, plus new code search and source-control access controls.
The catch: you can't use it. Anthropic says Scion is too closely tied to its internal setup to release, and only makes sense for giant monorepos with thousands of engineers and agents. Publicly, Claude Code still connects to GitHub rather than a hosted Anthropic forge.
Side-by-side
| Cursor Origin | OpenAI (Pando + Code Storage) | Anthropic Scion | GitHub | |
|---|---|---|---|---|
| Owner | Cursor / SpaceXAI | OpenAI | Anthropic | Microsoft |
| Can you use it? | Yes, beta on paid Cursor plans | Code Storage today; coming into Codex | No, internal only | Yes |
| Still Git? | Yes | Yes (new backend) | No (new VCS) | Yes |
| Main idea | Agent-native forge inside the editor | Horizontally scaled Git + machine-first storage API | Centralized, server-side VCS for a giant monorepo | General-purpose forge + ecosystem |
| Headline numbers | ~296K clones/hr, <400ms sync (early reports) | ~5x faster pushes, 99.99% merge reliability, ~1 PB/day | 200x less CPU/RAM, 30K+ merges/day | 30M+ new repos/month |
| GitHub interop | Two-way sync | Git-compatible | Migrated away | — |
| Biggest gap | Beta, code-custody questions, no full CI/packages | Not a standalone public product yet | Not available | Reliability |
Part 4: Is GitHub actually done?
No, and it's worth being fair here.
GitHub's response:
- After the August 17 outage, GitHub says it added 3+ million CPU cores, 120 petabytes of fast storage and significant network capacity, installing as much hardware as its datacenters' power allowed while speeding up the Azure migration.
- By September, Azure served 65.4% of read traffic for GitHub's core application, 48.3% of Git read traffic and 80.2% of stream processing.
- It's moving storage to Azure Blob, going multi-region, and pulling critical systems off shared databases. GitHub CTO Vladimir Fedorov told iTWire the company is finishing its Azure migration and called it a meaningful inflection point.
- GitHub's Kyle Daigle has said the backend work is focused on stability and resilience, rebuilding the hidden systems that do the core work.
GitHub's moat is not the Git host. As one developer put it in a widely shared essay, GitHub has alternatives, but no replacement: shared identities, contribution habits and discovery don't migrate with your repos. Origin, Codex and Scion solve hosting for agents and teams, not the social layer of open source.
What this means for you
- If you're a solo dev or small team: GitHub is still fine, but keep a mirror (Codeberg/Forgejo, GitLab, or Origin's sync) so an outage doesn't block you.
- If your team lives in Cursor: Origin is worth trying via two-way sync, with GitHub as the source of truth until custody terms and CI options mature.
- If you run lots of agents: watch how often they push. The lessons from Pando and Scion (independent branch coordination, server-side operations, fewer full clones) apply at much smaller scales than you'd think.
- If you run a big monorepo: read OpenAI's and Anthropic's engineering posts. They're the best public playbooks on source control for agents right now.
The bigger shift: code hosting is becoming part of the AI coding stack. Whoever owns the place where agent-written code lands owns the review, CI and data around it. That's why every major lab now wants its own.
Further reading
Primary sources
- Redesigning source control at Anthropic (Scion)
- Scaling Git at OpenAI (Pando)
- OpenAI to acquire Pierre Computer Company
- The August 17 outage, and the work ahead (GitHub)
- Addressing GitHub's recent availability issues
- GitHub availability report: October 2026
- Ghostty Is Leaving GitHub (Mitchell Hashimoto)
Coverage and analysis
- Cursor releases Origin as an agent-native alternative to GitHub (InfoQ)
- Cursor launches Origin as GitHub goes dark (The New Stack)
- How Anthropic redesigned source control for AI-driven development (InfoQ)
- OpenAI built itself a new Git backend, too (The New Stack)
- GitHub outages persist as AI coding drives traffic surge (The Register)
- Trigger, not root cause: GitHub's availability decline under AI-driven load (MDPI)
- GitHub has alternatives, but no replacement
- Hacker News discussion: Cursor launches Origin
Are you mirroring your repos anywhere yet, or still all-in on GitHub? Tell me in the comments. 👇



