Agent requests fail with "User is unauthorized" despite active Pro subscription

Support Bug Reports
1

Where does the bug appear (feature/product)?

Background Agent (GitHub, Slack, Web, Linear)

Describe the Bug

My Cursor Pro subscription is active and correctly recognized inside the application.

However, every Agent request fails immediately with:

ActionRequiredError: Unauthorized request. User is unauthorized

The issue affects all Agent conversations.

I have already:

  • Logged out and logged back in
  • Reinstalled Cursor completely
  • Deleted all local Cursor data
  • Cleared authentication data
  • Updated Cursor to the latest version

The subscription is active and shown as Pro inside Cursor, but Agent requests continue to fail with an authorization error.

Steps to Reproduce

  1. Open Cursor.
  2. Open Agent Window.
  3. Start a new Agent conversation.
  4. Send any message.
  5. The request immediately fails with:
    “Unauthorized request. User is unauthorized”

Expected Behavior

The Agent should process the request normally and return a response.

Screenshots / Screen Recordings

‏‏لقطة الشاشة (1666).png
‏‏لقطة الشاشة (1666).png1366×768 83.8 KB

Operating System

Windows 10/11

Version Information

Version: 3.8.11 (user setup)
VS Code Extension API: 1.105.1
Commit: e56ad3440df06d22ca7501e65fd518e905486ef0
Date: 2026-06-18T01:40:18.333Z
Layout: editor
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.256
OS: Windows_NT x64 10.0.22000

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

f9a7046a-279b-47e5-ab48-6e8dc12daba1

Additional Information

The issue persists even after a clean reinstall and deleting all local Cursor data.

My account is recognized as Pro and billing is active.

This appears to be an account authorization issue specific to Agent requests.

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report with the screenshot and Request ID. I can see the pop-up: “Unauthorized request / User is unauthorized”.

Good news: your account is fine. Your Pro subscription is active, and there are no blocks on the server side. In 99% of cases, this error with an active Pro plan is caused by a system clock mismatch. If your local time is noticeably off, the token is read as expired and the request gets rejected before it reaches the server. That’s why logging out, reinstalling, and clearing data didn’t help. Those steps don’t change your system clock.

Try this on Windows:

  1. Settings > Time & language > Date & time
  2. Turn on Set time automatically
  3. Click Sync now
  4. Make sure the time zone is set correctly
  5. Fully close and restart Cursor, then sign out and sign back in

In your screenshot, the tray shows the date as 2026/06/19, so it does look like the time is off. Syncing should fix it.

Let me know how it goes.