Cursor Origin
How to Create a Cursor Origin Repository and Push Code to It
Create an Origin repository at cursor.com/codebase with New, or ask a Cursor agent to create one through the Origin CLI. Then sign in with origin auth login, clone the repo over HTTPS from origin.cursor.com/{owner}/{repo}.git, and push with ordinary git. For code that already lives on GitHub, use Sync from GitHub instead.

On this page
How do you create a repository on Cursor Origin?
From the codebase home at cursor.com/codebase, select New, enter a Repo Name in the New repo dialog and select Create Repo. For a repo owned by a team codebase, the dialog also asks for Internal or Private visibility.
Check your plan first, because Free and Plus don't include Origin. You need Premium, Super or Ultra, a Teams or Enterprise plan, or a legacy Start, Pro, Pro+ or Ultra plan.
Pick the right button before you start. New creates an empty repository, which suits a fresh project. For code that already lives on GitHub, the same page has Sync from GitHub, and the docs send existing repos down that mirror path. The mirror keeps GitHub as the source of truth and lets you review its pull requests in Cursor. Pushing a GitHub clone into an empty Origin repo works, but you lose the sync.
- 1Open cursor.com/codebase and select New.
- 2In the New repo dialog, enter a Repo Name. For a team-owned repo, also choose Internal or Private.
- 3Select Create Repo.
- 4Open the new repo and copy the clone URL from the green Code button.
Visibility depends on who owns the repo. On a team-owned repo, Internal means visible to anyone on your team with access to the codebase, and Private means visible only to members granted access directly or through codebase permissions. A repo under a personal account is always Private, so the dialog skips the choice, and you share it by inviting people from its Collaborators settings. The dialog offers no public option. Cursor's release notes do mention public Origin repositories, but the docs don't say how a repo becomes public.
- Repo Name
- The last segment of the clone URL: https://origin.cursor.com/{owner}/{repo}.git
- Internal
- Team-owned repos only: visible to anyone on your team with access to the codebase
- Private
- Team-owned repos: visible only to members granted access directly or through codebase permissions. Personal repos are always Private.
- Settings after creation
- Team-owned repos: General, Access, Rules and Protections, and Apps. Personal repos: General, Collaborators, Apps, Rules and Protections, and Advanced.
From cursor.com/docs/origin/create-repository and the Origin settings page.
Team access follows your Cursor team and codebase access, and who may create repositories at all is set at the codebase level, in codebase settings. Check which level you're on before you look for a missing permission.
This is covered hands-on in Cursor Compile 2026 — 1 short Unit, free to read.
Rather do it than read about it? Run 11 interactive Cursor walkthroughs in a simulated editor. Free, no account needed.
Can a Cursor agent create the Origin repo for you?
Yes. Cursor's docs say agents can create Origin repositories as part of a task. Ask the agent in Cursor to create a repo on Origin, and it can install the Origin CLI, sign in, create the repo, set the remote and push. The command underneath is origin repo create, which the Agents and automations page names.
Agents use the same permissions as your Cursor account. The create succeeds only if your account has access to Origin code storage, and the agent can do only what your team's codebase permissions allow you to do. An agent asked to create a repo where you can't create one fails the same way you would.
Cloud agents are a different case. The docs say they can work against existing Origin repositories: clone, branch, commit and push. Their pull requests open wherever the repo's source of truth lives: on Origin for a repo created there, on GitHub for a mirror. The create step is described for a local agent with the CLI installed, so create the repo first and hand the cloud agent an existing one.
Whether you or an agent runs it, the repo is created with your account's access and lands in the same codebase, with the same visibility rules and the same Settings tab. Review what an agent created the way you would review what it pushed.
How do you clone, push and pull an Origin repo?
Origin works with standard git. Open a repo at cursor.com/codebase, select the green Code dropdown, and copy the clone URL from the HTTPS tab. HTTPS URLs take the form https://origin.cursor.com/{owner}/{repo}.git, and you clone one like any other repo.
git clone https://origin.cursor.com/acme/checkout.git
Over HTTPS, credentials are where the Origin CLI comes in, even if you never type another origin command. Cursor's install script puts it on your machine, and origin auth login signs you in through the browser. Per the command reference, that login also installs the git credential helper, so git push and git pull against Origin remotes need no further setup.
curl -fsSL https://downloads.cursor.com/origin/install.sh | sh origin auth login
Sign in before your first git operation over HTTPS.
The Code menu's SSH tab shows URLs such as git@origin.cursor.com:{owner}/{repo}.git for SSH clones. SSH authenticates with a public key on your Origin account, which you add with origin ssh-key add, passing the key file and a name with -t. On your first connection, compare the host key fingerprint with the ones on Cursor's Clone, Push & Pull page before you answer yes.
For a brand-new empty repo, the first push is the standard sequence: clone the empty repo, add files, commit, and push with -u so the upstream is set. If the project already exists locally, skip the clone and add Origin as a remote instead.
cd your-project
git remote add origin https://origin.cursor.com/{owner}/{repo}.git
git push -u origin mainPulling is git pull origin main, with nothing Origin-specific about it. The CLI also has origin repo clone, which clones over HTTPS with your saved login. It saves a step when you're already working in the CLI, but plain git clone with the credential helper in place does the same job.
Can you push to GitHub and Origin at the same time?
Yes. The docs show how to keep GitHub and Origin in parallel while you evaluate: add both hosts as push URLs on one remote, so a single git push updates both. Fetches still use the remote's original URL. This is a plain git feature, not an Origin one.
git remote set-url --add --push origin git@github.com:acme/checkout.git git remote set-url --add --push origin https://origin.cursor.com/acme/checkout.git
The docs follow that block with the more important sentence: "For a full history copy from GitHub into Origin, prefer mirroring." Two push URLs copy only the commits you push from this machine from now on. They don't copy pull requests, or anything a teammate pushes from a laptop without the second URL, because each clone keeps its own remote settings in .git/config. The mirroring page covers what the documented sync carries and what no git command ever will.
So the advice is narrower than the command suggests. Use two push URLs for a repo you created on Origin and want copied elsewhere, or for a solo trial. Use Sync from GitHub for anything a team already works on, and treat the two-URL setup as a personal convenience, not a team policy.
What do you do when clone or push fails?
The docs cover three failures. When a clone or push fails over HTTPS, their first check is that you're signed in. Over SSH, they check that the key you're using is on your account. A command not found after installation means the install location isn't on your PATH.
- Symptom
- git clone or git push over HTTPS fails against origin.cursor.com
- Fix from the docs
- Confirm you are signed in with origin auth login. It re-runs the browser sign-in and installs the git credential helper, which is set up per machine, so run it on each machine you push from.
- Symptom
- Clone or push over SSH fails
- Fix from the docs
- Check that your key is on your account with origin ssh-key list. If the connection stopped at the host key prompt, compare the fingerprint with the documented ones.
- Symptom
- origin: command not found after the install script
- Fix from the docs
- Add ~/.local/bin to PATH. For zsh, append export PATH="$HOME/.local/bin:$PATH" to ~/.zshrc, then run source ~/.zshrc.
- Symptom
- Create Repo is missing or disabled
- Fix from the docs
- Repository creation is a codebase permission an admin grants. Check codebase settings, not the repo.
| Symptom | Fix from the docs |
|---|---|
| git clone or git push over HTTPS fails against origin.cursor.com | Confirm you are signed in with origin auth login. It re-runs the browser sign-in and installs the git credential helper, which is set up per machine, so run it on each machine you push from. |
| Clone or push over SSH fails | Check that your key is on your account with origin ssh-key list. If the connection stopped at the host key prompt, compare the fingerprint with the documented ones. |
| origin: command not found after the install script | Add ~/.local/bin to PATH. For zsh, append export PATH="$HOME/.local/bin:$PATH" to ~/.zshrc, then run source ~/.zshrc. |
| Create Repo is missing or disabled | Repository creation is a codebase permission an admin grants. Check codebase settings, not the repo. |
The first three rows are the documented troubleshooting steps. The last follows from the codebase permission model the docs describe.
One more case looks like a bug and isn't. If you set up the credential helper with --local, it applies to that repository's git config only, so a second clone on the same machine prompts or fails until you sign in there too. The CLI reference lists the global and local variants. Global is the default, and on a personal machine it's the one to keep.
Frequently asked questions
How do I create a new repository on Cursor Origin?
Go to cursor.com/codebase and use New: name the repo, then confirm with Create Repo. A team-owned repo also needs Internal or Private, while a personal repo is always Private. Then copy the clone URL from the green Code button and push from your machine. A Cursor agent can run the same flow for you through the Origin CLI.
What is the clone URL format for an Origin repo?
Over HTTPS it is https://origin.cursor.com/{owner}/{repo}.git, shown on the HTTPS tab of the Code menu. Sign in first with origin auth login so the git credential helper is installed. The SSH tab shows git@origin.cursor.com:{owner}/{repo}.git, which authenticates with a key registered on your Origin account.
What is the difference between Internal and Private on Origin?
On a team-owned repo, Internal means visible to anyone on your team with access to the codebase, and Private means visible only to members granted access directly or through codebase permissions. Repos under a personal account are always Private. The New repo dialog has no public option.
Should I create an empty Origin repo and push my GitHub code into it?
Usually not. Cursor's docs point code that already lives on GitHub to Sync from GitHub on the codebase home. GitHub stays the source of truth, and you can still review its pull requests in Cursor. A manual push into an empty repo copies history but not the pull requests, and gives you no sync.
Why does git push to Origin fail with an authentication error?
Over HTTPS, the likely cause is a machine that hasn't run origin auth login, which installs the git credential helper on that machine. If the origin command itself isn't found, add ~/.local/bin to your PATH first. Over SSH, list your registered keys with origin ssh-key list.
Sources & last verified
- Cursor Docs: Create an Origin repository
- Cursor Docs: Clone, Push & Pull
- Cursor Docs: Install the Origin CLI
- Cursor Docs: Origin CLI commands
- Cursor Docs: Mirror a GitHub repository
- Cursor Docs: Origin
- Cursor Docs: Origin settings
- Cursor Docs: Origin agents and automations
- Cursor Docs: Origin release notes
Cursor ships frequently. Facts verified against primary sources on October 28, 2026.