Cursor Origin: Code Hosting Now in Early Beta

What Cursor Origin ships in its August 17 early beta

Code hosting is a service that stores a team's source code and lets people review changes to it. Cursor Origin is Cursor's own version, rolled out in early beta on August 17, 2026. Cursor describes the first release as "the essentials, designed for agent scale", with four parts: repos, pull requests, code browsing, and GitHub sync.

Repos start from the CLI and a codebase name

A repo (short for repository) is one project's files together with their change history. To make one in Origin, click +New and name it. A page then shows how to install the CLI, the command-line tool, with commands to clone a repo (copy it to your computer) or push a local project (upload it to Origin).

After you push, the code is hosted on Origin. You also name a codebase when you create your first repo, and that name becomes part of every repo URL, in the form cursor.com/codebase/acme-corp.

Pull requests put review next to the agents

A pull request (PR) is a proposal to merge one set of changes into a project. Every Origin repo has them. Opening one shows the timeline, commits, checks, and files changed.

A reviewer can read the diff (the line-by-line changes), leave comments, and merge. Cursor says "code, PRs, and agents are now in the same place." The changelog adds that you can ask Cursor questions about the code you are browsing, and that Cursor can answer, make changes, update PRs, or push a branch.

How Cursor Origin syncs with GitHub

GitHub sync brings a repo that lives on GitHub into Origin. Cursor says GitHub repos can sit alongside the ones it hosts. To set it up, connect GitHub to Cursor and pick your organization (org).

The repos you can sync then appear. Select one and Cursor pulls it in. You choose what gets synced, and you can disconnect a repo at any time.

Comments on synced repos travel in both directions

Pull requests on synced repos sync both ways. A comment written in Cursor posts to GitHub. A reaction or reply on GitHub shows up in Cursor within seconds.

If you are assigned to review a pull request on GitHub, you can review and merge it from Cursor. Synced repos also update in real time, and you can browse, search, and pull from the copy in Origin.

GitHub stays the source of truth for synced repos

The source of truth is the copy that counts when two copies differ. Pushes to a synced repo keep going to GitHub, and Cursor says GitHub stays the source of truth while Origin mirrors the result. Icons next to each repo name show which repos Cursor hosts and which came from GitHub.

Which Cursor plans include Origin during the beta

Cursor began rolling Origin out in early beta on paid plans on August 17. Enterprise organizations whose admins opt out do not get it.

Paid plans get it, except opted-out enterprise orgs

Cursor says the rollout covers all paid plan users. The exception is enterprise orgs whose admins opt out.

Agent-native features are listed as coming soon

Cursor's changelog says agent-native features "ship soon". It names no features and gives no date.

Vercel, Depot, and Buildkite integrations for Origin

Cursor says it is building an app ecosystem so a team's whole stack works with Origin. The August 17 changelog lists integrations with Vercel, Depot, and Buildkite as already available and says more are coming.

Vercel adds a preview deployment to every pull request

Connect Vercel from a repo's Apps tab, and every PR gets a preview deployment. A preview deployment is a test copy of the change where people can try it and leave comments. Once you merge, the change ships to production, the live version.

Depot and Buildkite run existing GitHub Actions workflows

For CI, Cursor says to connect Depot or Buildkite. CI (continuous integration) means automated checks that run on each change. Both run existing GitHub Actions workflows, which are the automated steps a repo already defines on GitHub. Buildkite also runs its native pipelines.

Cursor Origin vs GitHub: how TechCrunch framed the launch

TechCrunch's report covers the launch under the headline "Cursor capitalizes on GitHub frustration, launches rival hosting platform." The two points that follow come from TechCrunch's reporting, not from Cursor.

The same-day outage in TechCrunch's report

TechCrunch says the launch coincided with ongoing frustration over a perceived dip in GitHub's services. It adds that GitHub had a long worldwide outage on the same day Cursor launched Origin.

GitHub's 180 million developers, per GitHub's own metrics

TechCrunch's August 18 report cites GitHub's own metrics: some 180 million developers used GitHub as of October 2025. It also calls GitHub the largest source-code host in the world.

Paid Cursor teams get Origin unless admins opt out

Cursor Origin started in early beta on August 17 for paid plans, with enterprise orgs whose admins opt out as the exception. It has four parts: repos, pull requests, code browsing, and GitHub sync. On synced repos, pull request comments move in both directions, pushes keep going to GitHub, and Cursor says GitHub stays the source of truth.

Vercel, Depot, and Buildkite were listed as already available at launch, and the changelog gives no date for agent-native features. TechCrunch reported that the launch coincided with a lengthy GitHub outage. SpaceX Cursor Acquisition: Reading the Closing 8-K and AI Coding Agent Hijacked by a Fake Bug Report cover related Cursor and coding-agent news.