You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Cursor Origin shows "Could not verify" for a signed-in CLI because origin auth status --json needs field names #35624
I searched existing issues and did not find a duplicate.
I included enough detail to reproduce or investigate the problem.
Area
apps/server
Steps to reproduce
Install the current stable Origin CLI (2026.11.03-22-10-56-fbcd8ba) and sign in with origin auth login. origin auth status reports Token: valid.
Open Settings → Source control providers in T3 Code.
Look at the Cursor Origin row, or open the pull requests view in a project whose remote is on origin.cursor.com.
Expected behavior
Cursor Origin shows as authenticated, and Origin pull requests load.
Actual behavior
The row shows the detected CLI version, but says:
Could not verify Cursor Origin. Install the Origin CLI with curl -fsSL https://downloads.cursor.com/origin/install.sh | sh, then run origin auth login.
T3 Code checks the sign-in with origin auth status --json. The current Origin CLI requires --json to name its fields, and exits 1 otherwise. With no JSON on stdout, auth is reported as unknown, which the UI shows as the install hint. OriginCli.viewer runs the same command, so getViewer fails too and Origin pull requests do not load.
$ origin auth status --json
Error: Specify one or more comma-separated fields for`--json`:
authenticated
authMethod
source
endpoint
tokenValid
apiKeyPrefix
account
team
teams
organization
shadowedStored
reason
$ echo$?
1
From server.trace.ndjson:
PullRequestProviderError: cursor-origin failed in getViewer: Specify one or more comma-separated fields for`--json`:
at OriginCli.viewer
at OriginPullRequestProvider.getViewer
at PullRequestService.listUncached
Workaround
None in T3 Code itself. #33507 fixes this by passing --json authenticated,tokenValid,account.
Still reproduces on T3 Code (Nightly) 0.1.11-nightly.20261117.4851 with Origin CLI 2026.11.03-22-10-56-fbcd8ba (macOS). #33507 isn't merged yet, so the fix hasn't shipped.
Until it lands, this workaround on the user's side works for me. It replaces the installer's ~/.local/bin/origin symlink with a small wrapper that answers only the bare auth status --json call in the shape OriginAuthStatusSchema parses, and passes everything else (including the git credential helper) to the real binary:
It needs a T3 restart, because discovery runs at server start and then about every 5 minutes, and toggling the provider in Settings doesn't re-probe. Putting the wrapper earlier on PATH instead (for example ~/.local/shims) did not work for me: the server trace showed processRunner.runProcessCore spawning origin on every discovery, but it never ran the shim, so it has to replace ~/.local/bin/origin itself. An Origin self-update recreates the symlink and undoes it.
Activity
bedair81 commentedon Nov 12, 2026
fixed in #33507
gaodes commentedon Nov 18, 2026
Still reproduces on T3 Code (Nightly) 0.1.11-nightly.20261117.4851 with Origin CLI
2026.11.03-22-10-56-fbcd8ba(macOS). #33507 isn't merged yet, so the fix hasn't shipped.Until it lands, this workaround on the user's side works for me. It replaces the installer's
~/.local/bin/originsymlink with a small wrapper that answers only the bareauth status --jsoncall in the shapeOriginAuthStatusSchemaparses, and passes everything else (including the git credential helper) to the real binary:It needs a T3 restart, because discovery runs at server start and then about every 5 minutes, and toggling the provider in Settings doesn't re-probe. Putting the wrapper earlier on
PATHinstead (for example~/.local/shims) did not work for me: the server trace showedprocessRunner.runProcessCorespawningoriginon every discovery, but it never ran the shim, so it has to replace~/.local/bin/originitself. An Origin self-update recreates the symlink and undoes it.