Cursor Origin Hosted Codebases
Origin is Cursor's hosted-codebase surface at cursor.com/codebase. This page settles when you host a repo on Origin as the remote, and when GitHub stays the source of truth while Origin only mirrors it. The Cursor editor guide still owns Tab, Agent, and the files on disk.
What an Origin Codebase Holds
Cursor's 17 August 2026 changelog introduced Origin as code hosting: repos, pull requests, code browsing, and GitHub sync. The Codebase tab is the home for those repos. Agent-native extras were listed as coming later, so treat the essentials above as what shipped in the early beta.
The first repo you create also names the codebase. 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.
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.
When GitHub Stays the Remote
Mirroring copies a GitHub repository into Origin and keeps Origin updated as GitHub changes. 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 hosted-codebase surface at cursor.com/codebase. You browse repos and pull requests there. Tab, Agent, and local files stay on the Cursor editor guide.
Who can use Origin today?
Cursor's 17 August 2026 changelog says Origin is rolling out in early beta on all paid plans, except enterprise orgs whose admins opt out. The mirror docs name Pro, Teams, or Enterprise access. Teams on legacy privacy mode cannot enable Origin until they switch to Privacy Mode.
Does a GitHub mirror replace GitHub?
On a synced repo, GitHub stays the source of truth. 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 mirror copies git history, branches, tags, and pull requests. GitHub Issues, GitHub Actions workflows, and secrets stay on GitHub. Depot and Buildkite CI on Origin apply to Origin-hosted repos, not to mirrored ones.
Can I review GitHub pull requests in Cursor?
On a mirrored repo, pull requests sync both ways. 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?
Open the repo at cursor.com/codebase, copy the HTTPS URL from the Code menu, and clone
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 September 1, 2026.
Sources
-
[1]
Origin Code Hosting(cursor.com)
-
[2]
Cursor Origin(cursor.com)
-
[3]
Clone, push, and pull(cursor.com)
-
[4]
Mirror a GitHub repository(cursor.com)
-
[5]
Pull requests(cursor.com)
-
[6]
Codebase settings(cursor.com)
-
[7]
Origin settings(cursor.com)
Read Next
Beginner-friendly guide to Cursor, our #1 AI coding tool: its VS Code roots, Tab and Agent workflows, cloud agents, Grok Bot, diffs, models, pricing, setup, strengths, and limits.
The best AI coding tools compared for 2026: Cursor with Grok Bot, Claude Code, Codex, GitHub Copilot, OpenCode, and Google Antigravity. What each does well, current models, pricing, and how to choose.
How Grok Bot works next to Cursor: hand off a coding task from the editor, leave it running, and keep Tab, Agent, and your local files in place.
How Cursor Automations work in 2026: always-on cloud agents that run on a schedule or a trigger, with webhooks, no-repo monitors, Slack and GitHub actions, the template marketplace, what they cost, and how to wire one up for automated code review.