Repositories inside Cursor
Cursor began rolling out Origin, an early-beta code-hosting service, to paid-plan users on August 17, 2026. The first release includes hosted repositories, pull requests, code browsing and GitHub synchronization, placing source management alongside Cursor’s coding agents. Enterprise organizations can opt out through an administrator.
Origin repositories live under a new Codebase tab. A user names a codebase, creates a repository and receives command-line instructions for cloning it or pushing an existing local project. The chosen codebase name becomes part of repository URLs on `cursor.com`. Code pushed through that flow is hosted by Origin.
The service can also display GitHub repositories beside Cursor-hosted ones. After connecting a GitHub organization, users choose which repositories to synchronize and can disconnect them later. People with read or write permission on a synchronized repository can view its Origin copy. Icons distinguish repositories hosted directly by Cursor from those imported through GitHub.
For synchronized projects, GitHub remains the source of truth. Origin updates its browsable copy in real time, while pushes continue to GitHub. That design lets teams explore and pull code through Cursor without immediately moving an established repository away from its existing host.
Pull requests and agents in one workspace
Each repository includes pull-request views showing the timeline, commits, checks and changed files. Reviewers can inspect a difference, comment and merge. On synchronized repositories, pull-request activity travels in both directions: comments made in Cursor are posted to GitHub, while reactions and replies from GitHub appear in Cursor within seconds, according to the announcement. Assigned GitHub reviews can also be completed and merged from Cursor.
Cursor’s agent can answer questions about code being browsed, make changes, update pull requests and push a branch. The company says further agent-native features are coming, so the beta’s current capabilities should not be confused with its full planned design. The supplied announcement does not provide performance, reliability or scale measurements.
Origin also starts with deployment and continuous-integration connections. A Vercel integration can create preview deployments for pull requests and deploy after a merge. Depot and Buildkite can run existing GitHub Actions workflows, while Buildkite also supports its own pipelines. Repository settings show synchronization state, connected applications and access controls.
The launch puts Cursor in a role beyond code editing: it can host repositories directly or act as a synchronized interface over GitHub. The two paths reduce the immediate cost of trying the product. A team can create an Origin-native project, or keep GitHub authoritative while testing Cursor’s combined browsing, review and agent workflow.
Early-beta status remains the important qualification. Origin launches with the essentials the company identifies for agent-scale work, but adoption will depend on how access, synchronization and integrations perform under real development conditions.
