Not work with byok with cursor 2.4.22 version

Support Bug Reports
1

After I upgraded Cursor to v2.4.22, I found that the previous access via the BYOK method started throwing errors. What could be the reason for this? Does Cursor no longer support the BYOK mode?

Request ID: 0514c689-0c20-4a46-8c7d-0b8c6bdd236d

{“error”:“ERROR_UNAUTHORIZED”,“details”:{“title”:“Unauthorized request.”,“detail”:“No authorization header found”,“isRetryable”:false,“additionalInfo”:{},“buttons”:[],“planChoices”:[]},“isExpected”:true}

Unauthorized request. No authorization header found

kje: Unauthorized request. No authorization header found

at Gmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38045)

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE

  • Cursor CLI

  • Background Agent (GitHub, Slack, Web, Linear)

  • BugBot

  • Somewhere else…

Describe the Bug
After I upgraded Cursor to v2.4.22, I found that the previous access via the BYOK method started throwing errors. ERROR_UNAUTHORIZED

Steps to Reproduce

  1. upgrade to newest version

  2. talk in agent mode and got fail

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11

  • MacOS

  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy

  • For Cursor CLI: Run agent about in your terminal


Version: 2.4.22 (Universal)
VSCode Version: 1.105.1
Commit: 618c607a249dd7fd2ffc662c6531143833bebd40
Date: 2026-01-26T22:51:47.692Z

Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Darwin x64 23.4.0

For AI issues: which model did you use?
myself model, named “internal-model-sonnect-aws“

For AI issues: add Request ID with privacy disabled
Request ID: 0514c689-0c20-4a46-8c7d-0b8c6bdd236d

{“error”:“ERROR_UNAUTHORIZED”,“details”:{“title”:“Unauthorized request.”,“detail”:“No authorization header found”,“isRetryable”:false,“additionalInfo”:{},“buttons”:[],“planChoices”:[]},“isExpected”:true}

Unauthorized request. No authorization header found

kje: Unauthorized request. No authorization header found

at Gmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:38045)

at Hmf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9095:37251)

at rpf (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:4395)

at fva.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9096:8170)

at async Hyt.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34196:57047)

at async Zpc.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:7695)

at async Zpc.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34245:8436)

at async FTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9170:14575)

at async Ei (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32994:3808)

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable

  • Sometimes - I can sometimes use Cursor

  • No - Cursor works, but with this issue

2

Hi there!

We detected that this may be a bug report, so we’ve moved your post to the Bug Reports category.

To help us investigate and fix this faster, could you edit your original post to include the details from the template below?

Bug Report Template - Click to expand

Where does the bug appear (feature/product)?

  • Cursor IDE
  • Cursor CLI
  • Background Agent (GitHub, Slack, Web, Linear)
  • BugBot
  • Somewhere else…

Describe the Bug
A clear and concise description of what the bug is.

Steps to Reproduce
How can you reproduce this bug? We have a much better chance at fixing issues if we can reproduce them!

  1. …
  2. …
  3. …

Expected Behavior
What is meant to happen here that isn’t working correctly?

Screenshots / Screen Recordings
If applicable, attach images or videos (.jpg, .png, .gif, .mp4, .mov)

Operating System

  • Windows 10/11
  • MacOS
  • Linux

Version Information

  • For Cursor IDE: Menu → About Cursor → Copy
  • For Cursor CLI: Run agent about in your terminal
IDE:
Version: 2.xx.x
VSCode Version: 1.105.1
Commit: ......

CLI:
CLI Version 2026.01.17-d239e66

For AI issues: which model did you use?
Model name (e.g., Sonnet 4, Tab…)

For AI issues: add Request ID with privacy disabled
Request ID: f9a7046a-279b-47e5-ab48-6e8dc12daba1
For Background Agent issues, also post the ID: bc-…

Additional Information
Add any other context about the problem here.

Does this stop you from using Cursor?

  • Yes - Cursor is unusable
  • Sometimes - I can sometimes use Cursor
  • No - Cursor works, but with this issue

The more details you provide, the easier it is for us to reproduce and fix the issue. Thanks!

4

Hey, thanks for the report. This looks like an issue with sending the Authorization header in Agent mode after the update.

I’ll need a bit more info to debug:

  • Which BYOK method are you using?
    • IAM Role ARN
    • AWS Access Keys
  • What was the last version where this worked?

The “No authorization header found” error usually means Cursor isn’t passing credentials in the request. After updates, you sometimes need to re-validate your settings.

As a temporary workaround, if this is blocking you, try rolling back to stable 2.4.0 or 2.3.x while we look into it.

Let me know the validation results. If it still doesn’t help, I’ll pass it to the team with the details.

5

The BYOK method I’m using follows OpenAI’s approach, and after rolling it back to version 2.3.X, everything is now working properly.

6

also how to re-validate setttings in cursor? log out and login back?

7

I see you already figured out the rollback to 2,3.x. This looks like a regression bug in 2,4.22.

To share this with the team, can you clarify:

  1. How exactly is BYOK set up? (Override OpenAI Base URL in the model settings plus a custom endpoint?)
  2. Do you see the same error in Ask mode, or only in Agent?

About “re-validate settings”, in your case it won’t help because the issue is in 2,4.22 itself. Rolling back to 2,3.x is the right move until the team fixes it.

I’ll pass the report along with your details.

8

one more question: does this happen with non-BYOK models too, or only BYOK?

9

With BYOK configuration, I just used OpenAI’s Settings to set up my personal API Key and endpoint, and then used a custom model alias.

10

Thanks for the info. You’re using OpenAI settings with a custom endpoint and a model alias.

The team has already fixed this, but the fix hasn’t made it into a stable release yet. Rolling back to 2.3.x is the right move for now.

One quick question for the team: if you try the standard Cursor models in 2.4.22 (without BYOK), do they work normally, or do you get the same error? That’ll help us understand how widespread the issue is.