2026-04-26 Connection failed. Please try again, or contact support if the issue persists

Support Bug Reports
1

Request ID: dfd553a9-3f6c-4735-8e67-d47c9b9cc1b1
[unauthenticated] HTTP 401
l5t: [unauthenticated] HTTP 401
at Pf_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29433:24316)
at Rf_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29433:23144)
at Uf_ (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29434:6490)
at q0h.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29434:11307)
at async cQi.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41749:12418)
at async Vnm.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:12344)
at async Vnm.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41817:19567)
at async lCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29549:16906)
at async Object.Va [as onSubmit] (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:40805:4230)
at async vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:40804:100980

3

run diagnostics

image
image2238×1670 229 KB

6

Hey. From the diagnostics it looks like Authentication works on its own, but API, Ping, and Chat fail with quota_key. That means an invalid entitlement state got cached. This can happen with new Pro accounts when the client requests a token before the subscription fully syncs with Stripe.

Try this:

  • In Cursor: Cmd+Shift+P → Cursor: Sign Out, or via Cursor Settings > Account > Sign Out
  • Fully quit Cursor with Cmd+Q, not just closing the window
  • Open it again and sign in

The negative cache for quota_key usually lasts a few minutes, so if it doesn’t work right away, wait 5 to 10 minutes and try again.

If diagnostics still shows a 401 on the API after that, send a new Request ID from chat right upper corner > Copy Request ID after re-auth, and we’ll take a deeper look.

7

re install，problem solved

8

Glad to hear reinstalling fixed it. If it comes back, let me know with a new Request ID after you re-auth, and we can dig deeper.