Unauthorized request

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

Request ID: ed8f8c04-4983-4013-bbaf-0fe52273edf5
{“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
ActionRequiredError: Unauthorized request. User is unauthorized
at $gy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7547:82737)
at m_a (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7547:81651)
at lfy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:12878)
at Object.classify (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:17458)
at nfy (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:5856)
at async A_a.run (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7548:16810)
at async Sge.runAgentLoop (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7681:34738)
at async QMl.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18769:14657)
at async QMl.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:18769:32126)
at async i$e._submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.glass.main.js:7660:2525)

Request ID: ed8f8c04-4983-4013-bbaf-0fe52273edf5

Steps to Reproduce

Sending a prompt

Expected Behavior

After sending the prompt I should get a response back

Operating System

Linux

Version Information

Version: 3.16.29
VS Code Extension API: 1.128.0
Commit: 6246455961129c32969845e00aa25d87ae926ec0
Date: 2026-08-18T01:26:26.285Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Linux x64 7.0.0-30-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hey @_Kinus! Your account is fine and your Pro plan is active. The reason the request is rejected is that your computer’s clock is currently about seven weeks behind the real date (it’s reading late July), and our servers reject requests from a machine whose clock is that far off. It shows up as “User is unauthorized,” but signing out and back in won’t help while the clock is off.

To fix it on Linux:

  1. Close Cursor.
  2. In a terminal, run sudo timedatectl set-ntp true
  3. Run timedatectl and confirm “Local time” shows today (September 14) and “System clock synchronized: yes”. (Or in your desktop Settings → Date & Time, turn on “Automatic Date & Time”.)
  4. Reopen Cursor and send a prompt.

If it won’t sync or snaps back to July after a reboot, that usually means a flat CMOS battery, a VM/container restoring an old snapshot, or a network blocking NTP (UDP 123). Let me know if the error persists once the clock is correct.