Commands

Every origin command with its options, except pull requests and stacks, which have their own pages: Pull request commands and Stack commands. To see the same information in your terminal, run origin --help for the command list or origin <group> --help for one group. To install the CLI, see Install the CLI.

The Origin CLI (origin) is separate from the Cursor Agent CLI (agent) documented under CLI.

Global options

These work with any command:

The CLI reads the API endpoint and credentials from the environment, as CURSOR_ORIGIN_ENDPOINT, CURSOR_AUTH_TOKEN, and CURSOR_API_KEY. See Environment variables.

Command groups

Targeting a repository

Most commands infer the repository from the origin git remote in your current checkout. Override it with -R, --repo in org/name format, or set ORIGIN_REPO for the whole shell. -R wins over ORIGIN_REPO, which wins over the git remote:

origin pr list -R acme/checkout

Authentication

Manage your session and the git credential helper.

The CLI uses the first credential it finds: CURSOR_AUTH_TOKEN, then CURSOR_API_KEY, then a login stored by origin auth login. origin auth status shows which one is in use. In CI, set CURSOR_AUTH_TOKEN or CURSOR_API_KEY instead of signing in.

When CURSOR_API_KEY is set and you omit --api-key, origin auth login asks Log in with this API key instead of the browser? [y/N] and defaults to the browser flow. In a non-interactive shell, such as CI, it logs in with the key and prints a notice.

origin auth login also installs the git credential helper, so git push and git pull against Origin remotes work without further setup.

Repositories

Pass org/name to target a repository. origin repo create <name> without a slash creates the repository in your account's namespace.

origin repo from-github takes owner/repo, HOST/OWNER/REPO, or a URL. Without an argument, it reads the origin remote when that remote points at github.com.

origin repo view --json mirrorStatus tells you which forge owns a repository. no-mirror and outbound mean Origin owns it. Any other value means GitHub does. See Mirror a GitHub repo.

Repository access

origin repo access manages who can reach a repository: the owning team's groups, team members, organization groups, and external collaborators.

set and remove take exactly one subject:

Removing a repository grant leaves namespace-level grants alone. To change those, use origin namespace access.

Mirrors

origin repo mirror manages a repository's GitHub mirror.

Push local

On a repository mirrored from GitHub, origin push local sets up the origin-local remote at https://origin.cursor.com/{owner}/{repo}.git/local and pushes local origin/* branches there. Use this to keep working when GitHub is unavailable, or to store any other git state you want only on the Origin copy. It doesn't appear in origin --help. After the first run, that remote looks like:

origin-local    https://origin.cursor.com/{owner}/{repo}.git/local (fetch)origin-local    https://origin.cursor.com/{owner}/{repo}.git/local (push)

Other branches still go to GitHub with git push origin. See forge-local branches.

Labels

Manage the labels a repository defines. Add them to pull requests with origin pr create --label or origin pr edit --add-label.

origin label import reads the output of gh label list --json name,color,description, so you can copy a GitHub repository's labels in one step.

Rulesets

Manage the merge-time and push-time rulesets for a repository:

create and update take these options. Each repeatable option replaces the whole list:

To copy a ruleset between repositories, save origin ruleset view <id> --json name,enforcement,kind,includedRefNames,excludedRefNames,rules,bypassActors to a file and pass it to origin ruleset create --input with -R set to the target repository.

Namespaces

origin namespace access manages grants on a namespace, the org in org/repo. origin ns is an alias for origin namespace.

set and remove take exactly one of --team <admins|members>, --user <user> (a Cursor user ID, or the email of a user already granted on the namespace), or --group <id> (an organization group ID, as printed by list).

Apps

origin app manages Origin apps: their webhook subscriptions, signing keys, and webhook deliveries.

Redelivery is asynchronous. Run origin app webhook deliveries afterward to see the outcome.

SSH keys

Manage the SSH public keys on your Origin account:

API requests

origin api makes an authenticated request to the Origin REST API at api.cursor.com/v1/origin for anything without a first-class command. It supports request flags similar to gh api: -X, --method, -H, --header, -F, --field, -f, --raw-field, and --input. --verbose prints the request and response headers to stderr, and --silent drops the response body. To filter the JSON response, pipe it to jq. {owner}, {repo}, and {branch} placeholders expand from -R, --repo, the ORIGIN_REPO environment variable, or the origin git remote. See the Origin API docs for endpoints, authentication, and examples.

Agents

origin agent prompt prints a Markdown guide to origin for AI agents, written for the installed version. origin agent prompt <topic> prints one topic: auth, prs, review, ci, stacking, json, or reference. origin agent prompt reference pr lists every command in one group.

origin agent setup installs a skill that tells your coding agent to run origin agent prompt:

Updates

Update to the current release on your channel:

origin update

--force reinstalls even when you're already on the current version.

The CLI updates from the stable channel by default. Switch with origin config set-channel <latest|stable> and check with origin config get-channel.

Shell completion

Append the completion script to your shell config:

origin completion >> ~/.zshrc

Branch-valued flags such as --head and --base then complete local branch names.

Environment variables

Getting help

Every command takes --help:

origin --helporigin repo --helporigin repo create --help

Next steps

• Pull request commands
• Stack commands
• Install the CLI
• Create a repository
• Clone, Push & Pull