Cursor’s Origin Puts Code Hosting Inside the Editor, Without Asking Teams to Leave GitHub

Updated Oct. 26, 2026, 6:23 a.m. ET: Adds a link to our report on GitHub’s explanation of the outage.

GitHub has since traced the Aug. 17 outage to an autoscaling blind spot and a retry storm, as we reported.

Cursor wants to be where code lives, not just where it gets written. The AI coding company started rolling out Origin, its own code-hosting service, to paid users on Monday, with a pitch built around agents working in the same place as the repository and its pull requests.

“Your code, PRs, and agents are now in the same place,” Cursor’s changelog says. Origin lives in a new Codebase tab. Teams name a codebase, which becomes part of each repo’s URL, install a CLI and push. For repos created there, Origin is the source of truth. Every repo gets pull requests with a timeline, commits, checks and changed files, and developers can ask Cursor’s agent about the code on screen, have it revise a pull request or push a branch.

The launch is deliberately modest. Cursor calls it an early beta focused on “the essentials,” and says agent-native features will “ship soon.” It is available on all paid plans, except at enterprise organizations whose admins opt out.

GitHub stays in the loop

The more interesting design choice is that Origin doesn’t require a move. Teams can connect a GitHub organization and sync selected repos, which then update in real time inside Cursor. For those, GitHub remains the source of truth: pushes keep going to GitHub and Origin mirrors them. Pull request conversations sync both ways, so a comment left in Cursor posts to GitHub and replies on GitHub show up in Cursor within seconds, the changelog says.

Three integrations were ready at launch. Vercel creates a preview deployment for each pull request and ships to production on merge, while Depot and Buildkite handle CI and can run existing GitHub Actions workflows.

An awkward Monday for GitHub

Timing helped. About three and a half hours after the rollout began, GitHub’s status page showed a global degradation that lasted six hours and 42 minutes, with error rates near 20% on pull requests, issues and the API, VentureBeat reported. VentureBeat noted that launches are typically scheduled weeks ahead and there is no sign Cursor timed this one.

TechCrunch put the scale of the challenge in one number: GitHub says some 180 million developers use its platform. For now, Origin’s sync-first approach suggests Cursor expects most teams to try it alongside GitHub rather than instead of it.