I'm experiencing an authorization issue with Cursor Agent

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor Agent is showing an “Unauthorized request” error when I try to use Agent mode. The error message says “User is unauthorized”, and the Agent request is not processed.

Steps to Reproduce

  1. Open Cursor.
  2. Open Agent mode.
  3. Enter a prompt and send the request.
  4. Cursor displays “Unauthorized request – User is unauthorized”.
  5. The Agent does not process the request.

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Cursor version: Version 3.20.17
OS: Windows 10/11

For AI issues: add Request ID with privacy disabled

3868a858-0954-4ec2-a0de-c3297cf1fb1b

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey @Visibility_Live, thanks for the report, and for the screenshot with the request ID.

Good news: your account is fine and your Pro plan is active. Looking up your request IDs, the reason the request is rejected is that your computer’s clock is currently about two and a half days behind the real date and time. Our servers reject requests from a machine whose clock is that far off, which is what shows up as “Unauthorized request. User is unauthorized”. Signing out and back in won’t help while the clock is off.

To fix it:

  1. Close Cursor completely.
  2. Open Windows Settings, then go to Time & Language, then Date & time.
  3. Turn on “Set time automatically” and “Set time zone automatically”.
  4. Under “Additional settings”, click “Sync now”.
  5. Check that the date and time shown now match today (September 13) and your local time
  6. Reopen Cursor and send an Agent prompt.

If “Sync now” fails or the date snaps back to the wrong day after a restart, turn off “Set time automatically”, set the date and time by hand, and try Cursor again. A clock that keeps resetting on its own usually points to a flat CMOS battery on the PC, or a dual-boot setup where the other OS writes local time to the hardware clock.

Let me know if the error still appears after the clock shows the correct date.