Pull requests on Cursor Origin

If the repo you have open lives on Cursor Origin (origin.cursor.com), GitLane now treats it as Origin — not as GitHub that happens to fail. You can list pull requests, read them, reply on existing review threads, and merge, using the origin CLI you already signed in with.

Clone, fetch, and push still go through ordinary git (your credential helper or SSH). You only need Origin sign-in when you open the PRs tab.

Sign in once, in the Origin CLI

1. Install the Origin CLI if you don’t have it.
2. In a terminal, run origin auth login.
3. In GitLane, Settings → Accounts should show your Origin login. GitLane never asks you to paste an Origin token.

If origin isn’t on your PATH, the PRs tab tells you that — it won’t silently call gh instead.

Browse and read a pull request

1. Open a repository whose remote is origin.cursor.com (HTTPS or SSH).
2. Open the PRs tab. You get that repo’s Origin pull requests — title, number, and state.
3. Select one to read the body, branches, files, commits, and the diff.

You don’t need a GitHub account for this. Numbers are Origin’s own numbers for the repository.

Reply, resolve, merge

On an existing review thread you can reply, resolve, or reopen. GitLane refreshes the thread after Origin stores the change.

To land the PR, use the merge menu: Squash and merge or a merge commit. Origin doesn’t offer rebase-and-merge, and GitLane won’t delete the head branch after merge.

Good to know

You can’t yet create, edit, close, or approve an Origin pull request from GitLane, and you can’t start a new line-anchored comment. Those actions are hidden or refused outright — on an Origin repository GitLane never quietly falls back to the GitHub path.

Origin pull requests are not supported on native Windows. Use macOS, Linux, or WSL.

History, staging, and commit keep working even if you never open the PRs tab.

Shipped in GitLane v2.1.3.

Installers: Download GitLane.