Cursor CLI throws 403 but continues working

Bug Reports
1

Where does the bug appear (feature/product)?

Cursor CLI

Describe the Bug

cli throws 403 but works

Steps to Reproduce

cursor-agent “hello” --print --model auto

Error (unhandledRejection): HTTP 403: Invalid OAuth error response: SyntaxError: Unexpected token ‘F’, “Forbidden” is not valid JSON. Raw body: Forbidden
ServerError: HTTP 403: Invalid OAuth error response: SyntaxError: Unexpected token ‘F’, “Forbidden” is not valid JSON. Raw body: Forbidden
at parseErrorResponse (/Users/MYUSERNAME/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/index.js:152218:16)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async registerClient (/Users/MYUSERNAME/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/index.js:152786:15)
at async authInternal (/Users/MYUSERNAME/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/index.js:152278:33)
at async auth (/Users/MYUSERNAME/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/index.js:152230:16)
at async StreamableHTTPClientTransport.send (/Users/MYUSERNAME/.local/share/cursor-agent/versions/2025.11.06-8fe8a63/index.js:153404:36)

Hello. How can I help?

Expected Behavior

now error

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

2025.11.06-8fe8a63
2025.11.06-8fe8a63
2025.11.06-8fe8a63
2025.11.06-8fe8a63

For AI issues: which model did you use?

auto

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hey, thanks for the report. The error points to an issue in the OAuth registration flow, although it’s interesting that the CLI still keeps working.

Could you please clarify:

  • Does this happen on every CLI invocation, or only sometimes?
  • Are you behind a VPN, proxy, or corporate network?
  • Are you currently logged in to the Cursor agent?
  • Does running cursor-agent --version complete without errors?
  • Do you have any MCP servers that require authentication (for example: Linear, Notion, etc.)?

This looks like an error-handling issue in the OAuth flow that the team should take a look at.

3

  • Does this happen on every CLI invocation, or only sometimes?
    every. and in tui as well.

  • Are you behind a VPN, proxy, or corporate network? NO

  • Are you currently logged in to the Cursor agent? YES

  • Does running cursor-agent --version complete without errors? No errors. 2025.11.20-a4d3945

  • Do you have any MCP servers that require authentication (for example: Linear, Notion, etc.)? no mcp at all

4

I’ve had the same issue. After updating Cursor by installing the latest version, the error disappeared.