Cursor has begun rolling out Origin, its own code hosting service, moving the AI editor company directly into territory GitHub has held for more than a decade. The early beta opened Monday to paid subscribers, with enterprise organizations included unless their administrators opt out.
The initial release covers fundamentals rather than frills: repositories, pull requests, code browsing, and two-way synchronization with GitHub. Cursor frames that scope deliberately, describing Origin as hosting built for agent scale and saying agent-native capabilities will follow.
How it works
Repositories live under a new Codebase tab. Creating one opens an install flow for the command-line tool, along with the commands to clone a repo or push an existing local project. The name chosen for a codebase becomes part of every repository URL, following the pattern cursor.com/codebase/acme-corp.
Teams are not required to migrate. Connecting a GitHub organization surfaces the repositories available for syncing, and users pick individually which ones to pull in; any repo can be disconnected later. Synced projects update in real time and can be browsed, searched, and pulled from the Origin copy, while pushes continue to land on GitHub, which remains authoritative for anything that began there. Icons distinguish Cursor-hosted repositories from imported ones.
Pull requests that sync both ways
Every repository carries full pull request support, spanning the timeline, commits, checks, changed files, inline diff review, comments, and merge. On synced repositories that flow runs in both directions: a comment left in Cursor posts to GitHub, and a reply or reaction on GitHub appears in Cursor within seconds. Reviews assigned on GitHub can be completed and merged without leaving the editor.
That bidirectional design is the crux of the pitch. It lets Origin be adopted incrementally, one repository at a time, without forcing a team to abandon the GitHub workflows, permissions, and integrations it already depends on.
An ecosystem, not just a host
Cursor is assembling third-party integrations alongside the core product, with Vercel, Depot, and Buildkite live at launch. Connecting Vercel from a repository's Apps tab attaches a preview deployment to every pull request for testing and comment, shipping to production on merge. For continuous integration, both Depot and Buildkite execute existing GitHub Actions workflows, and Buildkite additionally runs its own native pipelines, a choice that lowers the switching cost considerably.
Why this matters
The strategic logic is about proximity. With code, pull requests, and agents in one place, Cursor can ask its models to answer questions about the repository being browsed, apply changes, update pull requests, or push a branch, operations that are awkward when the editor and the forge belong to different vendors.
It also lands at a moment of unusual leverage. Cursor was acquired by SpaceX in a $60 billion deal that closed this month, and Nvidia counts among its earlier backers, so the company has the balance sheet to sustain an infrastructure product that will take years to mature. The timing proved pointed in another respect as well, with Origin's debut coinciding with a significant GitHub outage.
Availability is staged rather than universal. Cursor's documentation places Origin on the Pro, Teams, and Enterprise tiers and excludes the free plan, with access opening in phases.
The unanswered questions are the ones hosting platforms are ultimately judged on: durability, granular access control, compliance posture, and migration guarantees. Origin ships with per-repository settings for sync status, access management, and connected apps, but a beta tuned for agent throughput is not yet a system of record. Cursor is betting that AI-native workflows will pull developers across that gap before the incumbents close it.
