Cursor launched its code hosting platform, Origin, for paid users on Monday morning. Three and a half hours later, GitHub experienced a six-hour global outage, disrupting pull requests, API access, and enterprise single sign-on. The timing was coincidental, but the incident highlighted growing frustration among developers over GitHub’s reliability.
Origin arrives as GitHub stumbles
The outage began at 11:18 UTC, with error rates near 20% across core functions and nearly 50% for archive downloads. An incident log noted failures in SAML, OIDC, and SCIM provisioning, along with Copilot. Enterprise users were locked out of critical workflows, drawing attention from the developer community.
Vercel CEO Guillermo Rauch posted on X: “You can now host your repos in Cursor Origin and deploy to Vercel via Cursor Origin which is itself hosted on Vercel. And unlike GitHub, it’s online 😁.” When asked why he was smiling, Rauch replied, “trying to make light of the situation. We ourselves are stuck because of github right now!”
Cursor’s Matt Palmer added, “We were going to ship this earlier, but GitHub was down.” The joke resonated, but the underlying concern was clear. For eighteen years, choosing where to host your team’s source code has been the least interesting decision an engineering organization makes. Cursor is betting that AI agents have made it interesting again—and for technical decision makers, that is the real news here.
What Origin offers
Origin operates inside Cursor’s editor, under a new Codebase tab. Teams name a repository, push code via the command line, and access standard forge features—pull requests, diffs, checks, and merges—without leaving the editor. The difference lies in how agents interact with the same interface, allowing developers to ask questions, revise pull requests, or push branches directly from their current code.
Three integrations debuted on launch day: Vercel for preview deployments, Depot for container builds, and Buildkite for CI. The latter two run existing GitHub Actions workflows unchanged, a deliberate choice. Cursor isn’t asking teams to rewrite pipelines; it provides a second view of code they already manage.
This compatibility defines the strategy. A forge without CI or deployments is just a code viewer. One that runs existing workflows and deploys to current infrastructure becomes a practical alternative.
GitHub remains the default source of truth
Cursor’s approach keeps GitHub in the loop. Origin doesn’t require teams to abandon GitHub. Instead, it mirrors repositories, syncing pushes, permissions, and pull request conversations in both directions. GitHub stays the authoritative source, while Origin serves as the workspace where developers spend most of their time.
Related: Tactile Technologies honors Womandla Women in STEAM
This design avoids the biggest barrier to enterprise adoption: migration risk. Rip-and-replace projects affect CI, compliance, audit trails, and team habits. A read-only mirror, however, costs nothing to test and breaks nothing if removed. If Cursor’s review experience proves superior, the source of truth may shift over time.
Key questions for engineering leaders
Origin is a beta, not a migration. Its sync mode lets teams evaluate whether an agent-native review surface improves cycle time without altering branch protections. Three questions require answers before moving anything authoritative.
- The default setting: Origin enables itself for paid users unless an admin opts out. Organizations that haven’t explicitly decided whether proprietary code can be mirrored to a new host have effectively had that decision made for them.
- The paperwork: Retention, residency, training use, subprocessors, and terms are all unpublished. Until those terms exist in writing, the defensible position is to treat Origin as a convenience layer over GitHub, not a system of record.
- The exit: Origin’s GitHub compatibility and source-of-truth design make adoption safe. But those same properties may erode as Cursor’s incentives shift toward owning the underlying infrastructure. Teams should ask what egress looks like now, while the mirror remains just that.
GitHub earned its dominance by being dependable infrastructure. For eighteen years, it hasn’t faced a serious challenge. Monday’s outage resolved at 20:22 UTC. Availability is an engineering problem, and those can be fixed. The question of who holds your source code, what they may do with it, and who they answer to carries no such resolution—and on that, the company selling trust has yet to publish its terms.
