Cursor Launches Origin Code Hosting Platform for Paid Users as GitHub Outage Hits 20%

Cursor launched Origin, a new code-hosting platform built to handle core developer workflows like collaborative coding, pull requests, code review, and repository storage, and it began rolling out to paid users starting Monday, August 18, 2026.

“GitHub suffered a global outage lasting roughly six hours and forty-two minutes”

The Cryptonomist

The rollout coincided with GitHub suffering one of its most damaging outages in recent history, with a global outage lasting roughly six hours and forty-two minutes and error rates near 20% and nearly 50% on file downloads.

36Kr

Cursor’s Origin is designed to interoperate with GitHub rather than replace it outright, letting teams sync existing GitHub repositories into Cursor’s platform while pushes keep flowing to GitHub.

Origin is accessed through a new “Codebase” tab within the Cursor editor, where developers can name a codebase, push to it from the command line, and get storage, permissions, checks, and merges layered on top of Git.

Cursor also positions Origin as part of an agent-centered workflow, stating in its changelog that “your code, PRs, and agents are now in the same place,” as it rolls out integrations with Vercel, Depot, and Buildkite.

Origin’s workflow keeps GitHub in the loop by allowing users to connect a GitHub organization, select repositories to sync to Origin, and disconnect at any time, with synced copies updating in real time while GitHub remains the source of truth for code changes started there.

At the pull request level, Origin provides a complete timeline, commit history, check items, and file change view, and the review loop can be completed directly within Cursor without opening a browser tab.

Bitcoin World

Cursor’s agent focus is central to the product architecture, with the claim that “35% of the PRs that have been merged on the Cursor platform were autonomously submitted by Agents running in cloud virtual machines.”

Cursor also describes a two-way sync experience where comments in Cursor are synced to GitHub and emoji reactions and replies on GitHub appear on the Cursor side within a few seconds.

In addition to repository hosting and review, Origin ties into deployment and CI via Vercel, Depot, and Buildkite, with Vercel creating a preview deployment for every pull request and Depot and Buildkite running existing GitHub Actions workflows without modification.

Cursor’s Origin launch also lands after Cursor became part of SpaceX, following an acquisition reported at roughly $60 billion in an all-stock deal that closed just days before Origin’s launch.

“Origin Ships With No Data Terms: SpaceX Now Holds Paid Developers Code”

Techzine Global

Techzine Global frames the stakes around code custody and policy, saying Origin shipped with “no published policy governing what Cursor does with that code,” and noting that Cursor has not published data retention terms, subprocessor disclosures, training-use policies, or migration tooling for code hosted natively on Origin.

The same reporting places the launch timeline at August 17, 2026, with early beta rolling out to users on all paid Cursor plans—Pro, Teams, and Enterprise—except enterprise organizations whose administrators explicitly opted out.

Origin’s architecture is presented as built for agent-scale development, with Cursor’s changelog and product descriptions emphasizing that code, PRs, and agents are housed together in the same interface and that Origin is included in paid Cursor plans during the early beta period.

With GitHub still receiving pushes for repositories synced into Origin and pull request conversations syncing in both directions, the next practical consequence in the sources is that teams can try Origin’s review experience while GitHub remains authoritative for repos started there, but Origin’s SpaceX ownership and unpublished data-handling terms add a new layer to the decision.