User in unauthorized

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using the Agent/Chat feature in Cursor IDE, every request fails with “Unauthorized request. User is unauthorized.” I use the same Cursor account across multiple MacBooks on some of them Cursor works completely fine, but on two newer MacBooks the Agent/Chat feature consistently fails with this error. Git operations (e.g. cloning repositories) work fine on the affected machines, so the issue seems specific to Cursor’s AI/authentication backend on those particular devices

Steps to Reproduce

  1. Sign in to the same Cursor account on multiple MacBooks
  2. On some MacBooks, Cursor Agent/Chat works normally
  3. On two specific (newer) MacBooks, open Cursor IDE and the Agent/Chat panel
  4. Type any prompt and submit it
  5. The request immediately fails with “Unauthorized request” this happens consistently on these two machines only

I have already tried the following troubleshooting steps on the affected MacBooks, none of which resolved the issue:

  • Signed out and signed back into my Cursor account
  • Fully quit and restarted the app
  • Verified my account status on cursor.com (account appears active)
  • Confirmed I’m on the latest version of Cursor
  • Confirmed git/network access works normally (cloning repos from GitHub works fine)
  • Reinstalled Cursor

The same account works fine on other MacBooks, which suggests the problem is device-specific rather than account-wide.

Expected Behavior

Agent/Chat requests should work the same way as on my other MacBooks where the same account is signed in, since the account is active and authenticated correctly, the two newer MacBooks should also be able to process Agent/Chat requests without an authorization error.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

IDE:
3.13.10
2026-07-23T21:41:07.333Z

MacOS:
Apple M5 Pro
Memory 128GB
macOS Tahoe 26,5,1

For AI issues: which model did you use?

Doesn’t matter which one.

For AI issues: add Request ID with privacy disabled

Request ID: 633e35ab-3d14-4f5a-b0da-d1dbb24e14a6
{“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 Kcb (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9450:6448)
at iIr (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9450:5416)
at zRm (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9451:12327)
at Object.classify (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9451:16859)
at Zcb (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9451:5856)
at async FOa.runWithSharedTurnRunner (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9451:16211)
at async Pq.runAgentLoop (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:12149:23038)
at async b1l.streamFromAgentBackend (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:18421:15130)
at async b1l.getAgentStreamResponse (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:18421:24972)
at async L5e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Users/lukas/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9615:2511)

Does this stop you from using Cursor

Yes - Cursor is unusable

Thanks for the detailed report!

This doesn’t look like an account problem. Your system clock is about 21 days behind real time, and our backend rejects requests with significant clock drift.

I confirmed this server-side on request 633e35ab-3d14-4f5a-b0da-d1dbb24e14a6. You can also see it in your own attachment: the screenshot is named Screenshot 2026-07-06 at 12.40.31.png though you posted it on July 27, because the machine thinks it’s July 6. Git works because it doesn’t check your clock, and your other Macs work because their clocks are correct.

The fix is normally to go to System Settings → General → Date & Time → turn on "Set time and date automatically, then confirm the date actually corrects to today. Restart Cursor and try again.

If the date doesn’t correct itself, something is blocking time sync (NTP, UDP 123 to time.apple.com). You can set the date manually to unblock yourself and have whoever manages the network or device profile allow it, or it’ll drift again.

Let me know if that clears it.

Thanks for insane fast reply! I will try and let you know