Cursor says it has begun rolling out Origin, a code hosting service built into its AI coding product, in early beta for all paid plans. According to Cursor’s changelog, the initial release covers the core workflows developers expect from a hosted code platform: repositories, pull requests, code browsing, and GitHub sync, with what the company calls “agent-native” features planned to follow. The launch puts code hosting directly inside Cursor rather than treating source control as an external surface. The new Codebase tab is the home for Origin repositories. Cursor says users can create a new repo from that tab, name it, install the command-line interface, then clone a repo or push a local project so the code is hosted on Origin. Cursor is also introducing a codebase naming scheme that becomes part of each repository’s URL. The company says users name their codebase when creating their first repo, and that name is then included in URLs under cursor.com/codebase. That makes Origin not just an editor-side feature, but a hosted destination for code projects inside Cursor’s own product surface. GitHub remains central to the first version. Cursor says users can connect GitHub, choose an organization, and select repositories to sync into Origin. The company says users choose what gets synced and can disconnect a repo at any time; users with read or write access to a synced repo can view it in Cursor. For repositories that originated on GitHub, Cursor says GitHub remains the source of truth: developers can browse, search, and pull from the Origin copy, while pushes continue to go to GitHub. Pull requests are part of the base feature set. Cursor says every repo has pull requests with timelines, commits, checks, changed files, diffs, comments, and merge controls. For synced GitHub repos, Cursor says pull request activity syncs both ways: comments made in Cursor post to GitHub, while reactions and replies made on GitHub appear in Cursor within seconds. The company also says GitHub reviews assigned to a user can be reviewed and merged from Cursor. The AI angle is that Cursor wants code, pull requests, and agents in one workspace. Its changelog says users can ask Cursor questions about code they are browsing, and that Cursor can answer, make changes, update pull requests, or push a branch. The company does not provide independent performance claims for those workflows in the supplied material, so the practical quality of the agent layer remains something users will have to test during the beta. Cursor is also positioning Origin as a platform for adjacent developer tools. The company says integrations with Vercel, Depot, and Buildkite are already available, with more integrations planned. Cursor says Vercel can be connected from a repo’s Apps tab so every pull request gets a preview deployment, while Depot and Buildkite can run existing GitHub Actions workflows; Buildkite can also run its native pipelines. The rollout is not universal across every organization by default. Cursor says Origin is rolling out to paid-plan users in early beta, except for enterprise organizations whose admins opt out. That caveat matters for companies that already have source-control governance, compliance, or workflow controls around GitHub and continuous integration systems. Who benefits: Cursor benefits if Origin increases paid-plan stickiness by moving more of the development workflow into its product. Paid Cursor users who already rely on the editor may benefit from fewer context switches across code browsing, pull requests, and agent-assisted changes. Who's exposed: GitHub is the obvious reference point, though Cursor’s first version still treats GitHub as the source of truth for synced repositories. Teams with strict enterprise controls may need to evaluate the beta carefully, especially around access, sync settings, and connected apps.