Cursor Agent failing with HTTP 403 permission_denied on both local and SSH (Request ID included)

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi Cursor team,

I’m encountering a persistent issue where Cursor Agent fails with:

[permission_denied] HTTP 403
RetriableError: [permission_denied] HTTP 403

This happens in both environments:

Local laptop (fresh install, re-login done)
Remote VPS over SSH (Cursor remote extension)

I have already tried:

Signing out and signing back in
Reinstalling Cursor
Switching networks
Verifying DNS/network connectivity
Testing on multiple machines

The issue persists in all cases.

Request ID:
fa331519-ec05-4593-839a-250fd72aa9c8

Expected behavior:
Cursor Agent should respond normally.

Actual behavior:
Agent fails immediately with HTTP 403 permission_denied.

Additional note:
Basic connectivity is working (internet, SSH, other services), but Cursor Agent requests consistently fail.

Could you please check if there is an issue with my account entitlement, feature flags, or backend access?

Thanks.

Steps to Reproduce

I open Cursor on both my local machine and a remote SSH workspace. After signing in successfully, I try to use Cursor Agent (default/Auto mode) in a chat. The request immediately fails with HTTP 403 permission_denied and a reconnecting loop. The issue happens consistently on fresh installs after signing out/in and does not depend on the project or prompt used.

Operating System

Linux

Version Information

Version: 3.8.11
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: Linux x64 6.8.0-124-generic

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the detailed report and the Request ID. That helped me look into it quickly.

Good news: your account is fine. Pro is active, and there are no issues with entitlements or feature flags. That’s why re-logging in, reinstalling, and switching machines didn’t change anything.

The issue is elsewhere: the request is being blocked at the network edge because of the region your connection is coming from. Cursor isn’t available in some regions that fall under US export controls and sanctions, and requests from those locations get rejected with HTTP 403 before they ever reach our servers, no matter what plan you’re on. Since both your local machine and the VPS over SSH are connecting from the same region, they hit the same restriction.

Unfortunately, this isn’t something you can fix on the client or account side. It’s tied to the network location. Sorry I can’t help more in this case.