Incorrectly throws "User is unauthorized" error

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Note: This persists after logging out and back in.

When utilizing the ide, suddenly I get a lot of errors saying I am unauthorized despite being confirmed logged in with the cursor settings, and shown as a Pro user. This is confirmed both in the IDE and the cursor account view. Unsure what can cause this.

Steps to Reproduce

Unclear as I cannot fix this

Expected Behavior

I am shown as an authenticated user that can make requests via the chat pane

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.43 (user setup)
VSCode Version: 1.99.3
Commit: 8e4da76ad196925accaa169efcae28c45454cce0
Date: 2025-10-30T18:49:27.589Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100

For AI issues: which model did you use?

unsure: auto

Additional Information

Request ID: 5a56d05f-0c77-4274-b98f-2a1de1eac231
{“error”:“ERROR_UNAUTHORIZED”,“details”:{“title”:“Unauthorized request.”,“detail”:“User is unauthorized”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
ConnectError: [unauthenticated] Error
at Fqc.$endAiConnectTransportReportError (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4984:399337)
at uwo._doInvokeHandler (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:490:36007)
at uwo._invokeHandler (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:490:35749)
at uwo._receiveRequest (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:490:34514)
at uwo._receiveOneMessage (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:490:33336)
at qDt.value (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:490:31429)
at _e._deliver (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
at _e.fire (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
at hgt.fire (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:4969:12156)
at MessagePort. (vscode-file://vscode-app/e:/Cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7492:18403)

Does this stop you from using Cursor

Yes - Cursor is unusable

2

Closing this as a restart fixed this. My suspicion is there was something weird when I was testing date-based logic and changed my system date to the future, and somehow Cursor would not update back to the current date. Going to assume this is more something weird with my system not cursor for now.

3

Thanks for sharing this! System date changes can sometimes interfere with auth. Glad a restart resolved it.