Cursor Origin Hosted Codebases

Cursor Origin hosts Git repositories and pull requests at cursor.com/codebase. You can create a repository with Origin as its main remote, or mirror an existing GitHub repository while GitHub remains the source of truth.

I would start with a new side project or a mirror before moving a team's code hosting. The important choice is where pushes, reviews, and CI actually happen. The Cursor editor can work with local files regardless of which service hosts their Git remote.

What Is Cursor Origin?

Origin is Cursor's Git hosting service, currently in early beta. It provides repository storage, code browsing, pull requests, integrations, and access for cloud agents. Its name is separate from origin, the conventional name of a Git remote that can point to any hosting service.

You claim a codebase namespace during setup; it cannot currently be renamed during the beta. That name becomes part of the URL, in the shape cursor.com/codebase/acme-corp. Codebase settings apply across the team's Origin repos. A repo still has its own Settings tab for sync status, access, and apps.

• Open the Codebase tab, choose New, and name the repo.
• Install the Origin CLI if you want the documented clone and push commands.
• Icons next to each repo name show whether Cursor hosts it or GitHub is the source.

Host a Repo on Origin

For a repo created on Origin, Origin is the source of truth. Pushes land on Origin, and GitHub stays off that path. Cursor documents standard git over HTTPS at https://origin.cursor.com/{owner}/{repo}.git.

Use the clone command for a new checkout. The alternative git remote add example is for an existing local project with no remote named origin. Replace the example URL with the repository you created; do not run both alternatives in the cloned directory.

origin auth login
git clone https://origin.cursor.com/acme/checkout.git

# Or add the remote to a local project
git remote add origin https://origin.cursor.com/acme/checkout.git
git push -u origin main

The same docs offer a dual-push remote while you evaluate GitHub and Origin in parallel. For a full history copy that should keep GitHub as source of truth, use the mirror flow instead of a second push URL.

I would host a new side project on Origin first, because the remote, the pull request, and the Cursor agent sit in one place. I would not move a team GitHub org until someone has cloned, pushed, and merged one real change on a disposable repo.

How Does Origin Mirror a GitHub Repository?

Cursor Origin mirrors GitHub history and updates, while ordinary pushes still reach GitHub first. Use it when the code already lives on GitHub and you want Origin browse, search, and pull requests on that history. Cursor's mirror docs require the Cursor GitHub app plus GitHub admin access on the source repo.

Repo Kind	Source of Truth	GitHub's Role
Origin-hosted	Origin	Not on the push path
GitHub mirror	GitHub	Pushes still land there
Detached copy	Origin after detach	Unchanged, no longer synced

A mirror includes git history, branches, tags, and pull requests. It does not include GitHub Issues, GitHub Actions workflows, or secrets. If you only want review comments on GitHub pull requests, BugBot does that without moving storage.

Detach from GitHub under Settings, then General, then Danger Zone. That stops the sync and turns the Origin copy into a standalone hosted repo. The original GitHub repository stays in place after detach.

Review and Ship from Origin

Every Origin repo includes a pull-request list. Open the Pull Requests tab to see the list, then open a row for activity, commits, checks, and files changed. You can request reviewers, comment on lines, and merge once reviews and CI are satisfied. Cursor cloud agents can also open pull requests on Origin as part of a task.

• Origin-hosted pull requests stay on Origin through comment, review, and merge.
• Mirrored pull requests sync both ways with GitHub comments and replies.
• Stay on GitHub Issues and Actions when those are still the team's source of work.

On a mirrored repo, pull requests sync both ways. Comment in Cursor and it posts to GitHub. Reply on GitHub and it shows up on Origin. Pull requests opened on a repo created directly on Origin stay on Origin.

Apps such as Vercel, Depot, and Buildkite install at the codebase level. Vercel can attach a preview to a pull request. Cursor's settings docs say Depot and Buildkite run on Origin-hosted repositories. Mirrored repos keep their CI running on GitHub.

The Smallest Hosting Move

Host a new repo on Origin when Cursor should be the remote and the team can live without GitHub Issues and Actions on that project. Mirror an existing GitHub repo when the team still needs GitHub as the source of truth and only wants browse, search, and two-way pull requests inside Cursor.

Skip a wholesale org migration until one hosted repo and one mirrored repo have each survived a real push, review, and merge. Origin is still in early beta, so admins can disable it, and the permission UI can still change.

FAQ

Is Origin another Cursor editor feature?

Origin is Cursor’s Git hosting service, separate from the editor’s local editing features. The Cursor editor handles your local editing workflow; Origin stores repositories and provides browser-based code and pull-request views.

Who can use Origin today?

Cursor Origin is available on Premium, Super, Ultra, Teams, and Enterprise, plus eligible legacy paid Cursor plans. Free and Plus do not include it. Team administrators can disable access, and Legacy Privacy Mode is unsupported. Check Origin access requirements before setup.

Does a GitHub mirror replace GitHub?

A Cursor Origin mirror does not replace GitHub: it keeps GitHub as the source of truth unless you detach it to create a standalone Origin repository. Pushes pass through to GitHub, and Origin mirrors the result. Detach from GitHub only when you want the Origin copy to become a standalone hosted repo.

What does a mirror leave on GitHub?

A Cursor Origin mirror leaves GitHub Issues, GitHub Actions workflows, and secrets on GitHub. It copies Git history, branches, tags, and pull requests. Depot and Buildkite CI on Origin apply to Origin-hosted repositories, not mirrored repositories.

Can I review GitHub pull requests in Cursor?

You can review GitHub pull requests through Cursor Origin when the repository is mirrored and the pull requests are synced. A comment in Cursor posts to GitHub, and a GitHub reply shows up on Origin. Pull requests opened on a repo created directly on Origin stay on Origin.

How do I clone an Origin repo?

Developers can clone a Cursor Origin repository by opening it at cursor.com/codebase, copying the HTTPS URL from the Code menu, and cloning https://origin.cursor.com/{owner}/{repo}.git. Sign in with origin auth login before the first git operation if the clone or push fails.

Where to Go Next

• Cursor guide for the editor this hosting surface sits beside.
• Best AI coding tools for how Cursor ranks against the other tools.
• Grok Bot works next to Cursor for the cloud teammate that can leave the editor.
• Cursor Automations for scheduled agents that already run on Cursor cloud.

Hosting, mirror, and pull-request facts were checked against the cited Cursor Origin pages on October 16, 2026.