Cursor launches Origin for repository hosting

• Origin is Cursor's early-beta git forge for hosting repositories, browsing code, reviewing pull requests, and sharing projects with a Cursor team, according to minchoi's launch post.
• A new repo starts in Cursor's Codebase tab, then moves through ordinary clone and push commands, as ericzakariasson's walkthrough shows.
• Existing GitHub projects can be mirrored into Origin while GitHub stays the source of truth, with minchoi's GitHub sync post describing the two-way pull request connection.
• Agents can answer questions about a repo, make changes, update pull requests, and push branches, the minchoi's agents post says.
• Origin's Vercel integration turns pull requests into preview deployments and merges into production deployments, a flow visible in minchoi's Origin demo.

Cursor is moving into the code-hosting layer beneath its editor. In a reply, minchoi called the move “the great consolidation” minchoi's reply. The Origin launch note includes a CLI workflow and a GitHub mirror, while the Origin documentation spells out what comes across and what stays behind. Vercel's announcement adds automatic preview and production deployments.

Origin lives in Cursor's new Codebase tab. Users click New, name a repository, install the CLI, and then clone the repo or push an existing local project. The first codebase name becomes part of each repository URL, such as cursor.com/codebase/acme-corp, according to Cursor's launch note.

The Origin repository docs also support creating an empty repo by asking a Cursor agent to do it. New repositories can be marked Internal or Private, then managed with standard Git commands.

Origin is designed to sit beside GitHub rather than demand an immediate migration. Users connect GitHub, choose an organization and repository, and select which projects to mirror. The copy in Origin updates as the GitHub repository changes, while pushes from a synced Origin repo pass through to GitHub.

The mirror documentation defines the boundary:

• Included: Git history, branches, tags, searchable code, and pull requests.
• Not included: GitHub Issues, GitHub Actions workflows, and GitHub Actions secrets.
• Source of truth: GitHub remains authoritative for a mirrored repository until it is detached.

Pull requests sync in both directions. Detaching converts the Origin copy into a standalone Origin-hosted repository, and pushes there stop flowing back to GitHub, the docs say.

Every Origin repository gets a pull request area with the activity timeline, commits, checks, changed files, diff review, comments, and merge controls. Cursor's pull request documentation describes the workflow as pushing a branch to Origin, opening a PR against the base branch, then reviewing it in the browser.

On mirrored repositories, comments and reactions move between Cursor and GitHub within seconds. A review assigned in GitHub can be completed and merged from Cursor.

The current agent surface attaches directly to that repository and PR context. Cursor says agents can answer questions about browsed code, make changes, update pull requests, or push a branch minchoi's agents post. Its integration docs add Automations and cloud agents that can review, change, and push code on Origin repositories.

Origin's Apps tab connects a repository to Vercel. Each Origin pull request can generate a Vercel Preview deployment for testing and comments, while merging triggers a Production deployment, according to Vercel's public-beta announcement.

Cursor's launch note lists Depot and Buildkite as additional integrations. Depot and Buildkite can run existing GitHub Actions workflows, while Buildkite also supports its native pipelines. The product is therefore shipping storage, review, agent execution, and deployment hooks as one repository workflow, rather than treating hosting as a separate tab in the toolchain.

Origin began rolling out on August 17 in early beta for paid Cursor plans, except enterprise organizations whose administrators opt out, Cursor says in its changelog. The documentation describes the beta as supporting repository creation, Git operations, GitHub mirroring, code search, pull requests, and team sharing.

GitHub mirroring requires Origin access on a Pro, Teams, or Enterprise plan, the Cursor GitHub app connected to the relevant organization or account, and GitHub admin access to the source repository, according to the mirror setup guide. Vercel's separate announcement limits its Origin connection to Pro customers in the public beta.