Request ID: fbf7f60c-6c75-4514-8535-e4b2e466d82d
{“error”:“ERROR_UNAUTHORIZED”,“details”:{“title”:“Unauthorized request.”,“detail”:“User is unauthorized”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:,“analyticsMetadata”:{“actionRequired”:“login”}},“isExpected”:true}
User is unauthorized
Unauthorized request. User is unauthorized
Rut: Unauthorized request. User is unauthorized
at Cqk (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36274:26826)
at lOy (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36274:25971)
at Rqk (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36275:6852)
at DNp.run (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36275:11720)
at async rge.runAgentLoop (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47623:65527)
at async _bf.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47691:12112)
at async _bf.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:47691:19276)
at async Zut.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/PC/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:36407:17835)
Hey, thanks for the report. The backend says your session token is expired or invalid actionRequired: "login". Your account is fine, you just need to re-auth.
Try this step by step:
- Sign out fully: File > Sign Out or Cursor Settings > Sign Out.
- Sign in again.
- If it still happens, check your system clock. On Windows: Settings > Time & Language > Date & time > turn on “Set time automatically”. Time drift often causes this unauthorized error.
- If it still doesn’t work, restart Cursor after you re-auth.
Let me know if it helped. If not, please share your Cursor version: Help > About, and we’ll take a look.
I’m getting the exact same error, and your recommendations didn’t help. I can’t even log in via the browser; the same “unauthorized” error appears. So, I can’t get back into my account after logging out.
Request ID: 3d33db2e-ad2a-40a6-8cc2-b1f4b5e47be5
{“error”:“ERROR_UNAUTHORIZED”,“details”:{“title”:“Unauthorized request.”,“detail”:“User is unauthorized”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:,“analyticsMetadata”:{“actionRequired”:“login”}},“isExpected”:true}
Unauthorized request. User is unauthorized
ActionRequiredError: Unauthorized request. User is unauthorized
at H2_ (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11960:27337)
at fEc (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11960:26488)
at bNb (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11961:11416)
at Object.classify (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11961:15921)
at j2_ (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11961:5707)
at async Z1m.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11961:15273)
at async TH.runAgentLoop (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:21241:3042)
at async Znh.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24418:13682)
at async Znh.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:24418:22527)
at async nRe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/npankratov/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12046:2087)
Hey, if you’re getting a 401 on cursor.com in the browser, not just in the IDE, it’s almost always caused by your system clock being out of sync. That breaks token validation everywhere, so you can’t log in.
Check the clock on your machine (npankratov, Windows):
- Settings > Time & Language > Date & time
- Turn on Set time automatically and Set time zone automatically
- Click Sync now
- Restart your browser and Cursor, then try logging in again
If the time is definitely correct and you still get a 401 in both the browser and the IDE, we’ll need to do a personal account-specific check.
Let me know if syncing the clock fixed it..
Clock synchronization didn’t help.
@Waggoner_Rohland, since syncing your clock didn’t help and you’re getting a 401 in both the browser and the IDE, this looks account-specific and needs a direct lookup, which we can’t do from the forum.
Thanks for reaching out. For account and billing requests, please email our team at [email protected]. They’ll be able to check your specific situation.
i am facing similar issues and done time sync. i am unable to even run the program since i cant login.
I have already dropped an email to [email protected] on friday 26 July 2026 and they have yet to get back since. please help.
Hey, thanks for the screenshots. The 401s on cursor.com in the browser (not just the IDE) confirm this is account-specific. Your token isn’t validating anywhere, and since the clock sync didn’t help, it needs a direct lookup we can’t do from the forum.
You’ve already done the right thing by emailing [email protected]. That’s where this gets handled. They work through requests in order, so it may take a little while over the weekend, but they’ll get back to you and check your specific account.
No need to send a second email. It won’t speed things up, and it could push the thread back in the queue. Hang tight and they’ll follow up.
I have been experiencing the exact same error. I checked the device time and tried using different devices and browsers, but the error persists. I have already contacted support via [email protected] but haven’t received a reply yet. I subscribed to the PRO plan, but I am unable to use it due to this error. @deanrie can you help me?