Provider error issue

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

An unexpected error occurred on our servers. Please try again, or contact support if the issue persists. Request ID: 254f5b9b-3d75-44e8-9623-bd8eb41115fd
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble finding the resource you requested. If the problem persists, please contact support.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
NonRetriableError: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
at Ydb (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9462:6779)
at PIr (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9462:5416)
at cMm (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:12870)
at Object.classify (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:17484)
at shb (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:5856)
at async g4a.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:16836)
at async Nq.runAgentLoop (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12161:24049)
at async p0l.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:18433:15130)
at async p0l.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:18433:24972)
at async W5e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9627:2511)

Steps to Reproduce

  1. Open Cursor and load the project.
  2. Set the model selector to Auto.
  3. Submit a prompt or trigger code generation.
  4. Result: An error occurs when Auto is selected.
  5. Note: If I manually select a specific model instead of Auto, it works normally without any error.

Operating System

Windows 10/11

Version Information

Version: 3.13.25 (user setup)
VS Code Extension API: 1.128.0
Commit: 31e8d61c448c7472e371505838a0fe34083dad50
Date: 2026-07-28T06:17:45.069Z
Layout: Agent Window
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.26200

For AI issues: which model did you use?

auto mode

For AI issues: add Request ID with privacy disabled

Request ID: 254f5b9b-3d75-44e8-9623-bd8eb41115fd
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble finding the resource you requested. If the problem persists, please contact support.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
NonRetriableError: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
at Ydb (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9462:6779)
at PIr (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9462:5416)
at cMm (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:12870)
at Object.classify (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:17484)
at shb (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:5856)
at async g4a.runWithSharedTurnRunner (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9463:16836)
at async Nq.runAgentLoop (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12161:24049)
at async p0l.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:18433:15130)
at async p0l.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:18433:24972)
at async W5e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/onur/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9627:2511)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

5

Hey, thanks for the detailed report with the Request ID, it makes the issue clear. This isn’t something in your setup. It’s a server-side issue with how Auto routes requests in a specific chat. It gets stuck on that conversation, so Auto fails there, while selecting a model manually still works.

For now, there are two workarounds:

  • Start a new chat, the issue shouldn’t happen in a fresh conversation.
  • Or stay in the current chat, but pick a specific model manually instead of Auto.

I’ve passed this to the team and we’re tracking it. I can’t share an exact timeline yet, but I’ll post here when there’s an update. Let me know if it still happens even after starting a new chat.

7

when i start new chat its fixed sir ty.