By Cursor rolled out Origin — its built-in Git hosting platform — to all paid users on the morning of August 17. About three and a half hours later, GitHub suffered one of its worst global outages in years: seven hours and 47 minutes, error rates hitting 20% across pull requests, Issues, and the API. Cursor did not time this on purpose. The internet noticed anyway.
The timing looks like marketing genius. It is just luck — which makes the underlying story more interesting, not less. Origin would be significant without the outage backdrop.
What Origin Ships With
The beta is four things: repositories (native or mirrored from GitHub), pull requests, code browsing inside the Cursor editor, and two-way GitHub sync. The core design choice is that agents are native to every repo — same surface as the code and the PRs they are modifying. No toggling between editor and browser mid-task.
The number that explains the design priority: 35% of pull requests merged inside Cursor are already opened by autonomous agents running in cloud VMs. Origin is built for that reality, not retrofitted to it.
Stacked PRs are also here, and they are good. Cursor acquired Graphite — the stacked PR startup — in December 2025. The result is a parentPullNumber API that chains dependent changes and a merge endpoint that collapses entire stacks in one call. Teams shipping multiple dependent features no longer have to wait on sequential approvals before unblocking the next change.
What Cursor Origin Does Not Have Yet
This is a beta, and a young one. No public repositories. No free tier. No first-party CI — Vercel, Depot, and Buildkite connect in for native Origin repos, but if you are mirroring from GitHub, your Actions workflows stay on GitHub. GitHub Issues do not migrate. The agent-native merge queue Cursor demoed in June is not shipped yet. For mirrored repositories, Cursor’s own documentation states GitHub remains the source of truth.
- Origin has: native agent integration, Graphite-backed stacked PRs, editor-native code browsing
- GitHub has: Issues, a mature Actions ecosystem, public repos, a free tier, published data terms
The Data Terms Gap
Origin rolled out opt-out by default, not opt-in. SpaceX now holds the code of paid Cursor developers on Origin. Cursor has not published data retention terms, subprocessor disclosures, or a policy on whether hosted code will be used to train models. For individual developers this is a low-stakes concern. For enterprise teams with compliance requirements, it is a blocker — and a strange oversight for a product shipping under a $60 billion parent company.
The SpaceX Factor
The $60 billion all-stock deal — the largest startup acquisition on record — closed August 14, three days before Origin launched. SpaceX folded Cursor into its SpaceXAI division. Origin is the first major product drop post-acquisition.
The harder question is not the data terms — those will get published. The harder question is model access. Claude is currently the most popular model inside Cursor. Anthropic already cut off xAI from accessing Claude after xAI engineers were found using Cursor as a route to tap Claude for competitive work. SpaceX has a financial incentive to prioritize Grok. No public commitment to multi-model access has been made. That is worth weighing before you migrate your repositories.
This Is Not a Feature Drop — It Is an Infrastructure Bet
Origin is a structural bet on owning the full developer stack: editor, Git hosting, and CI/CD. GitHub owns version control. Cursor is coming for it from the agent layer up.
Gartner projects 40% of enterprise applications will ship with task-specific AI agents built in by the end of 2026. When agents write the majority of pull requests, whoever controls where those PRs land controls the workflow. GitHub knows this — Copilot exists. But Copilot is bolted on. Origin bakes agents in from the start.
Vercel CEO Guillermo Rauch captured the moment 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.” It was a joke. It was also a signal of which way infrastructure-layer partnerships are bending.
Should You Try Cursor Origin?
If you are running agent-heavy workflows inside Cursor on a small team, Origin is worth piloting. The stacked PR workflow is genuinely better than the standard GitHub approach for dependent changes. The editor-native code browsing eliminates a real class of context-switching friction.
If you are evaluating it as a GitHub replacement for production teams: wait. The missing data terms, absent Issues, lack of first-party CI, and the open question on long-term model access are not small gaps. They are the gaps that determine whether Origin is a competitor or just a feature of Cursor that lives next to your GitHub tab.
The GitHub outage was not Cursor’s doing. But the fact that developers spent seven hours asking whether it was time to move is a signal worth taking seriously — regardless of who caused the outage.
