What Cursor Origin's code hosting ships in early beta
The company behind an AI code editor now hosts the code itself. Start with what exists today rather than what the launch post gestures at.
Repos start from the CLI and a codebase name
Origin repos live in the Codebase tab. Creating one and naming it produces a page with CLI install steps and the commands to either clone the repo or push an existing local project. Naming the codebase is a separate step from naming the repo, and it is the codebase name that sticks: the codebase name you set when creating your first repo becomes part of every repo URL after it, in the form cursor.com/codebase/acme-corp. That makes it the naming decision worth pausing on.
"Click +New to create a new repo and name it. Once you do, a page shows you how to install the CLI, with commands for how to clone a repo or push a local project. Push, and your code is hosted on Origin." (Origin Repos)/"Name your codebase when you create your first repo. That name becomes part of every repo's URL: cursor.com/codebase/acme-corp." (Origin Repos)— from Cursor's changelog
Pull requests put review next to the agent
Every repo gets pull requests. Opening one shows the timeline, commits, checks, and files changed, and the diff can be reviewed, commented on, and merged in place. Cursor's framing is that code, PRs, and agents are now in the same place. Cursor says asking it about the code you are browsing can go past an answer: it can make changes, update the PR, or push a branch.
"Every repo has pull requests. Open one to see the timeline, commits, checks, and files changed. Review the diff, leave comments, and merge." (Pull requests)/"Your code, PRs, and agents are now in the same place. Ask Cursor questions about code you're browsing. It can answer, make changes, update PRs, or push a branch." (Agents in every repo)— from Cursor's changelog
How GitHub sync works in Cursor Origin
Headlines called it a GitHub rival. The design does not ask anyone to switch.
Synced repos carry comments in both directions
Connecting GitHub and picking an organization produces a list of syncable repos. Only the selected ones get pulled in, and any of them can be disconnected later. Synced repos update in real time, and the Origin copy can be browsed, searched, and pulled from. Pull request activity moves both ways: a comment written in Cursor posts to GitHub, and a reaction or reply on GitHub appears in Cursor within seconds. A review assigned on GitHub can be finished and merged from Cursor.
"Your GitHub repos can sit alongside the ones Cursor hosts. Connect GitHub to Cursor, pick your org, and you'll see the repos you can sync. Select one and Cursor pulls it in. You choose what gets synced and can disconnect a repo at any time." (Bring your GitHub repos)/"Pull requests on synced repos sync both ways: comment in Cursor and it posts to GitHub, react or reply on GitHub and it shows up in Cursor within seconds. Got a review assigned to you on GitHub? Review and merge it from Cursor." (Pull requests)— from Cursor's changelog
GitHub stays the source of truth for synced repos
This is the line that decides how much risk trying Origin carries. Pushes to a synced repo keep going to GitHub, and GitHub remains the source of truth for anything that started there. What Origin holds is a live entry point for reading and working, not a replacement. Icons beside each repo name separate the ones Cursor hosts from the ones that came in from GitHub, so the two never blur together in the list.
"Synced repos update in real time. Browse, search, and pull from the copy in Origin. Pushes keep going to GitHub, which stays the source of truth for anything started there. Icons next to each repo name tell you which ones Cursor hosts and which came from GitHub."— from Cursor's changelog
Which plans get Origin, and what connects to it
Eligibility is decided by plan, and a small set of third-party services already plugs in.
Early beta covers paid plans except opted-out orgs
The rollout began August 17 for all paid plan users. The only carve-out is enterprise organizations whose administrators opt out. Free plans are not included. As for what comes next, Cursor commits to agent-native features shipping "soon" without naming either the features or a date, which is worth reading as a roadmap note rather than a promise you can plan around.
"We're starting with the essentials, designed for agent scale: repos, pull requests, code browsing, and GitHub sync. Agent-native features ship soon." (opening summary)/"Origin is rolling out in early beta to all paid plan users starting today, except enterprise orgs whose admins opt out." (availability note)— from Cursor's changelog
Vercel, Depot, and Buildkite connect from the Apps tab
App integrations arrived with the launch. Connecting Vercel from a repo's Apps tab gives every PR a preview deployment to test and comment on, and merging ships it to production. For CI, the options are Depot and Buildkite. Both run your existing GitHub Actions workflows, and Buildkite additionally runs its own native pipelines. Cursor describes this as the start of an app ecosystem, with more integrations to follow.
"We're building an app ecosystem so your whole stack works seamlessly with Origin. Integrations with Vercel, Depot, and Buildkite are already available, with more coming soon." (App extensions intro)/"Connect Vercel from a repo's Apps tab and every PR gets a preview deployment where you can test and make comments. Merge, and it ships to production. For CI, connect Depot or Buildkite. Both run your existing GitHub Actions workflows and Buildkite also runs its native pipelines." (App extensions detail)— from Cursor's changelog
The changelog splits its scope by feature heading, and the boundary of the early beta is easy to misread if those headings collapse. Converting the page to Markdown keeps the structure intact and gives you a baseline to diff against when the agent-native features are announced.
Summary
Cursor Origin is an early beta aimed at putting code, pull requests, and agents in one place. What exists today is repos, pull requests, code browsing, and GitHub sync, with agent-native features still ahead. Because pushes to synced repos keep landing on GitHub, trying Origin does not require committing to a migration. Access is paid plans only, minus enterprise orgs that opted out. TechCrunch tied the timing to a GitHub outage the same day, while noting that GitHub's own metrics put some 180 million developers on the platform as of October 2025; Origin is two days into an early beta and has published no comparable figure. Cursor's corporate footing has been shifting too, which we covered in SpaceX's acquisition of Cursor, and for the attack surface these coding agents open up, see our write-up on Agentjacking.
"The launch of Origin coincides with ongoing frustration over a perceived dip in GitHub's services. Indeed, on the same day that Cursor launched its new platform, GitHub suffered a quite lengthy worldwide outage." (the outage)/"According to GitHub's own metrics, some 180 million developers use its platform as of last October. The platform, which was founded in 2007 and acquired by Microsoft in 2012, continues to be the largest source-code host in the world." (GitHub's scale)— from TechCrunch



