On the morning of Monday, August 17, Cursor began rolling out a new feature called Origin to all paying users: a code-hosting service, in early beta, with an opt-out for enterprise plans. About three and a half hours later, GitHub suffered a global service degradation that lasted 6 hours and 42 minutes, with error rates on some features approaching 20%.
The two events aren't causally linked, but landing on the same morning made a stronger case than any product launch could.
What it actually offers
A new Codebase tab has appeared in the interface, where users can create and manage repositories, with local projects cloned or pushed via CLI; repo addresses take the form cursor.com/codebase/<name>. The full pull-request workflow has been ported over: timelines, commit history, check status, file diffs, review comments, and merges — PRs assigned to you on GitHub can be reviewed directly inside Cursor.
The relationship with GitHub is two-way sync. Once a GitHub organization is connected, existing repositories sync into Origin; comments written in Cursor get posted to GitHub, and comments made on GitHub sync back. The official line is that GitHub remains the source of truth, pushes still go directly to GitHub, and users can disconnect at any time.
Third-party integrations already in place include Vercel, Depot and Buildkite, covering preview deployments and CI pipelines.
The review workflow wasn't built from scratch. In December 2025, Cursor acquired Graphite, a code-review startup; that team and its technology now underpin Origin's review workflow. The acquisition looked at the time like a feature bolted onto the editor — in hindsight, it looks more like Cursor stocking up for a hosting layer.
Why now
For the past few years, Cursor's position has been "a layer sitting on top of GitHub." When an agent finishes editing code, it opens a PR; the PR has to go through GitHub; review comments have to be read on GitHub; the tool then syncs the results back into the editor. Every extra round trip across systems in that chain eats into the agent's usable context and adds latency.
Pulling the hosting layer in-house saves less in network requests than it gains in control over product definition. As the primary author of code shifts from humans to agents, the shape of a repository should shift with it: who can see which files and when, how a single change gets split up, who a review gets shown to — all of these rules are currently set around human collaboration habits. Origin's own marketing line about being "designed for agent scale" is describing exactly this layer.
The window on GitHub's side is genuinely open. Microsoft bought GitHub in 2018 for $7.5 billion in stock; eight years on, its role in the age of AI coding is fairly awkward — it has to host everyone's code, sell its own Copilot, and open APIs to a pile of competing agents at the same time. August's outage, lasting more than six hours, poked a hole in the implicit assumption that "hosting equals infrastructure."
The odds on this bet
Realistically, nobody is going to move their repositories off GitHub because of Origin in the short term. Open-source projects' issues, stars, forks, CI configurations and external-contributor habits are all rooted in GitHub; the migration cost sits on the social side, and the technical part is actually the easiest to solve. Cursor knows this too, which is why the first version is about syncing, not replacing.
Where it has better odds is inside enterprise repositories. Private code doesn't need a community or external PRs — companies only care whether agents run fast, whether the review process is smooth, and whether they can drop a subscription. Cursor's paying users are already concentrated in that segment, and Origin sits right inside their existing workflow, with an adoption barrier close to zero.
A rough calculation makes the point too. For a 200-person company, GitHub Enterprise runs into five figures a year on a per-seat basis, and Cursor's subscription is a separate line item — the overlap between what the two products do is expanding fast, covering reviews, CI triggers and code browsing, all of which Origin now handles. At renewal time, companies only need to ask one question: is it necessary to keep paying for both? The answer hinges on whether Origin's stability can hold up, not on whose feature list is longer.
There's a capital-structure factor behind all this too. Cursor now sits under SpaceX, and the parent company's cash flow can support an unprofitable hosting service for years — a completely different game from a startup that still has to answer to its funding rounds.
The metric to watch isn't in the release notes: how many companies, six months from now, have made Origin their primary repository rather than a synced copy. Syncing is a transitional state; the primary repository is the conclusion.
Sources: Cursor official changelog, SiliconANGLE, CocoLoop, Slashdot; verified beta access scope, GitHub's 6-hour-42-minute outage duration and error-rate framing, and the timing of the Graphite acquisition.