PR: https://git.cafe/pingdotgg/t3code/pulls/24639
GitHub: https://github.com/pingdotgg/t3code/pull/24639
Verification date: 2026-10-28
main: 1f8530ec3c (github/main)
PR head: 38a9b92cc5fbe825d3dbeb89af2e5229b685771d

Eligibility: OPEN, not merged. No PR commits authored by juliusmarminge or t3dotgg.
Changed behavior: Cursor /v1/me HTTP 403 except plan_required may omit identity while preserving models and authenticated status. 401 and other failures remain errors.

$ cursor-agent status
Not logged in
$ node -e "console.log(Boolean(process.env.CURSOR_API_KEY))"
false
No authenticated Cursor account or Enterprise API key was available.
No mock endpoints, placeholder API keys, fixtures, or demo data were used.

MAIN
$ git worktree add ../main github/main
HEAD is now at 1f8530ec3c
$ timeout 600 vp i
exit 0
$ T3CODE_DEV_SEED=0 setsid nohup vp run dev > /tmp/dev-main.log 2>&1 &
Captured PID: 16451
[dev-runner] serverPort=16733 webPort=8693 baseDir=/home/user/main/.t3
Chrome + repo Playwright: Settings > Providers > Add provider > Cursor.
Observed: Not authenticated. Sign in with Cursor or add CURSOR_API_KEY in provider settings. 0 models.
Original enterprise 403 could not be reproduced without real credentials.
Stopped main by captured process-group PID before starting PR.

PR
$ git switch --detach 38a9b92cc5fbe825d3dbeb89af2e5229b685771d
$ timeout 600 vp i
exit 0
An initial root-checkout dev launch selected ~/.t3; stopped immediately after startup log inspection, before client use.
Restarted with an explicit isolated home:
$ T3CODE_DEV_SEED=0 setsid nohup vp run dev --home-dir /home/user/t3code/.t3 > /tmp/dev.log 2>&1 &
Captured PID: 22268
[dev-runner] serverPort=13773 webPort=5733 baseDir=/home/user/t3code/.t3
Chrome + repo Playwright: Added Cursor through Settings. After client reload, no-key status remained Not authenticated, 0 models.
Created project from local folder /home/user/t3code through Add project > Local folder.
Selected Codex GPT-6.1-Sol in composer. Submitted read-only request through actual web client.
Real provider ran git rev-parse HEAD and git status --short:
  commit: 38a9b92cc5fbe825d3dbeb89af2e5229b685771d
  tracked files clean; git status --short returned no output.
  PR24639_CODEX_OK
Follow-up in same thread read CursorSdkCatalog.ts and returned:
  accountBlocked is true when cause is CursorSdkError, HTTP 403, code != plan_required.
  PR24639_FOLLOWUP_OK
Reloaded client; both messages persisted.

REMOTE FOCUSED CHECKS (Blacksmith)
$ vp i && vp test run packages/provider-cursor/src/server/status.test.ts packages/provider-cursor/src/server/CursorSdkCatalog.test.ts
2 files passed, 15 tests passed, exit 0.
Stored PR CI at head: 28 successful, 0 failing, 0 pending.
No source changes, commits, or pushes.

VERDICT
Core Cursor enterprise behavior remains UNVERIFIED. Codex turns and no-key Cursor status are neighboring checks, not proof of the changed Cursor 403 fallback.
Need a real Cursor Enterprise account whose /v1/me is blocked while /v1/models and agent execution work. Also unverified: real Cursor 401/plan_required/server-error cases, browser sign-in, desktop/mobile, relay/tunnel.