origin-cli

The CLI for Cursor origin.

DO NOT try to push to this repo using GitHub, your changes WILL be lost. Instead, push using the remote https://origin.cursor.com/git/anysphere/origin-cli.

Build / Install

To install the origin-cli to your system, run in the project root:

bun install
bun run build
npm install -g .

Usage

There are many sub commands under auth, repo, and change. Run co [auth|repo|change] --help to find them.

co <command>

Commands:
  co auth  Manage authentication
  co change  Manage changes
  co repo  Manage repositories

Options:
  --version     Show version number                                    [boolean]
  --auth-token  Cursor auth token (used directly as bearer)             [string]
  --endpoint    API server endpoint
                                 [string] [default: "https://origin.cursor.com"]
  --help        Show help                                              [boolean]

Helpful commands:

• co auth login — session token via Cursor login
• co auth setup-git — credential helper for origin.cursor.com
• co repo clone <org>/<repo> — clone via Origin HTTPS
• co repo set-origin-remote — point origin at Origin (replaces legacy co repo migrate)
• co repo trigger-ci <org>/<repo> --ref <ref> --sha <sha> — trigger CI for a ref/SHA

Changes (like GitHub pull requests)

Change commands use the same targeting shape as gh pr view: optional [number] or branch, -R org/name for repo (default: infer from git origin remote), or omit both to use the open/draft change for the current branch.

co change create <org>/<repo> \
  --title "…" --headRef <branch> --baseRef main --status open

co change view [number]              # summary; add --diff, --checks, -c/--comments
co change view 13 -R anysphere/origin-cli --comments
co change update [number]            # snapshot new version after push
co change mergeability [number]       # CI, approvals, conflicts
co change review [number] --approve -b "LGTM"
co change comment [number] -b "…"

co change view --json emits change metadata by default; add --diff, --checks, or --comments to include those fields (like composing gh pr view --json fields).

Agent-oriented docs: AGENTS.md.

Buildkite

Manage Buildkite pipeline triggers for a repository via co repo buildkite:

co repo buildkite <command>

Commands:
  co repo buildkite list <repo>                      List configured triggers
  co repo buildkite add <repo>                       Add or update a trigger
  co repo buildkite set-enabled <repo> <triggerId>   Enable or disable a trigger
  co repo buildkite delete <repo> <triggerId>        Delete a trigger

Examples:

co repo buildkite list myorg/myrepo
co repo buildkite add myorg/myrepo --buildkite-org cursor --pipeline my-pipeline
co repo buildkite add myorg/myrepo --buildkite-org cursor --pipeline my-pipeline --no-trigger-on-prs --branch-filter main --branch-filter 'releases/*'
co repo buildkite set-enabled myorg/myrepo <triggerId> --enabled true
co repo buildkite delete myorg/myrepo <triggerId> --yes