Skip to content
Cursor Handbook

Cursor Origin

Cursor's own git forge. Host repositories, mirror them from GitHub, review pull requests and point cloud agents at the result, all inside the account you already pay for.

  • Early beta
  • Pro, Teams, Enterprise
  • Not on free plans

Checked against cursor.com on 25 September 2026

What it does today

  • Host repositories

    Create Origin repos from the web, the CLI, or by asking a Cursor agent to do it. Origin is the source of truth for repos created this way.

  • Standard git

    Clone, push and pull with the git you already have. Signing in through the CLI installs a credential helper, so no token juggling.

  • Mirror from GitHub

    Sync an existing GitHub repository into Origin. GitHub stays the source of truth for synced repos, so nothing about your current workflow changes.

  • Pull requests

    Open, review and merge pull requests inside Origin rather than exporting the work elsewhere.

  • Browse and search

    Read code in the browser at cursor.com/codebase, including search across the repositories your team has access to.

  • Wire up agents

    Connect automations and cloud agents directly to Origin repos, and install Origin Apps from repository settings.

Why Cursor built a git host

The reasoning is easier to see once you look at where agents spend their time. A cloud agent that opens a pull request has to authenticate against a forge, clone from it, push to it, and read review comments back out of it. Every one of those steps currently crosses an integration boundary with permissions to negotiate and rate limits to respect.

Origin removes the boundary for teams that want it removed. When Cursor hosts the repository, an agent asking to create a repo, set a remote and push is one authenticated system talking to itself. Cursor's documentation makes this explicit: ask the agent to store a project on Origin and it can install the CLI, sign in, create the repository, set the remote, and push, without you leaving the editor.

Two kinds of repository

This is the distinction that determines whether Origin is a migration or an addition, and the repo list shows it with different icons.

  • Origin-hosted. Created in Origin. Origin is the source of truth. Your history, branches and pull requests live here.
  • Synced from GitHub. Mirrored in. GitHub stays the source of truth. You get Origin's browsing, search and agent wiring while your canonical repository, your CI, and your team's habits stay where they are.

For most teams the second option is the sensible way to evaluate the product. Nothing about the existing workflow has to change, and if Origin turns out not to fit, there is nothing to unwind.

Claiming a namespace

Before anyone can create a repository, one person has to claim a codebase name. That name becomes the owner segment of every Origin URL your team uses:

https://cursor.com/codebase/{owner}/{repo}

Any team member can claim it, which is worth knowing before an enthusiastic colleague claims something ill-considered on a Friday afternoon. During the beta the namespace cannot be changed or updated after it is claimed. Decide the name as a team first, then have someone run the flow.

Once claimed, admins create repositories and grant access from codebase settings, and can disable Origin for the whole team from the dashboard if they decide against it.

The Origin CLI

Origin ships its own binary, origin, which is a different program from the Cursor agent CLI. Confusing the two is the most common early mistake, because both install into ~/.local/bin and both want you to sign in.

The useful property is the credential helper. Signing in through origin auth login configures git itself, so git push and git pull against Origin remotes work without tokens, SSH keys, or a keychain prompt every morning.

Repository management runs through origin repo. Creating without a slash puts the repository in your own namespace; deleting always requires the full org/name, which is a deliberate asymmetry that makes accidental deletion harder.

Who should wait

Anyone on a free plan, because Origin is not available there. Anyone whose team is on legacy privacy mode, because that blocks enablement outright until the team switches to Privacy Mode. And anyone who needs a guaranteed stable namespace, since the no-rename constraint during beta is a real operational risk for a company that might rebrand or restructure.

Read from the Origin documentation on 25 September 2026. Beta features change quickly; check the source before relying on any of this.

Frequently asked questions

What is Cursor Origin?
Origin is Cursor's git forge: a place to host repositories, sync projects from GitHub, browse code in the browser, and open pull requests. It is Cursor's own hosting layer rather than an integration with someone else's.
Is Cursor Origin free?
No. Origin code storage is available on Pro, Teams and Enterprise plans and is explicitly not available on free plans. Access also opens in stages during the beta, so a paid plan does not guarantee you see it the moment it ships.
Does Origin replace GitHub?
It does not have to. Origin supports two kinds of repository: Origin-hosted repos, where Origin is the source of truth, and repos synced from GitHub, where GitHub remains the source of truth. Mirroring lets you use Origin's browsing, search and agent integration without moving your canonical repository.
How do I enable Origin for my team?
Someone has to claim a codebase name first. That name is the namespace your repositories live under, the owner segment in cursor.com/codebase/{owner}/{repo}. Any team member can claim it by opening cursor.com/codebase and choosing Get Started. Admins can then create repositories and grant access from codebase settings.
Can I change my Origin codebase name later?
Not during the beta. Cursor's documentation states you cannot change or update the namespace after it is claimed, which makes the first person to run the setup flow responsible for a decision the whole team lives with. Agree the name before anyone claims it.
Why can my team not enable Origin?
The most common cause is legacy privacy mode. Teams on legacy privacy mode cannot enable Origin and have to switch to Privacy Mode first. Separately, admins can disable Origin for a team from the dashboard at any time.
What is the Origin CLI, and is it the same as the Cursor CLI?
They are different binaries. The Cursor agent CLI is `agent`; the Origin CLI is `origin` and handles repository management. Install Origin's with curl -fsSL https://downloads.cursor.com/origin/install.sh | sh, then run origin auth login.
How does Origin handle privacy?
Origin follows the Privacy Mode setting of the namespace owner, meaning the team or individual who owns the repository. There is no separate per-repository privacy toggle to reason about.

Keep reading