Every repository Origin hosts comes attached to Cursor's agent and its review tool, so code review and further edits never leave the product.
Cursor has begun hosting code itself. Origin, its new service, is in early beta on all of the company's paid plans, and it handles repositories, pull requests and code browsing, plus two-way synchronization with GitHub.
Origin does not have to be the only place a team's code lives. A user can bring a GitHub-linked codebase into Origin, which sets up a live mirror sending changes through to both services; because pull requests synchronize in both directions, a team can shift its day-to-day development work into Origin while formally remaining on GitHub. By Cursor's account, GitHub remains the system of record for repositories kept in sync, while Origin's architecture is built to support a gradual migration of teams away from it.
The rest of the pipeline is wired in rather than rebuilt. Vercel handles preview deployments, while Depot and Buildkite provide continuous integration by running a team's existing GitHub Actions workflows without rewriting them.
GitHub was down the day Origin arrived — the platform's second major issue that month, with some functionality experiencing performance problems for over six hours. That Cursor meant to expand into GitHub's territory was already known before the launch; the two landed on the same day.
The reach is narrow for now. At launch the beta was open only to Cursor subscribers who pay, and the further capabilities meant for heavy agent-native workloads are slated for a later release, with no timing given beyond soon.