Request TimeOut

Support Bug Reports
1

Request ID: 409fe5a2-0b06-40fa-8f8c-e2183263d5f7
{“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”:true}
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
$Ai: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
at p9A (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23670)
at h9A (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at w9A (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at rau.run (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async GOa.runAgentLoop (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46834:10206)
at async _5u.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46888:9277)
at async _5u.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:46888:13663)
at async vMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
at async Ea (vscode-file://vscode-app/c:/Users/KIRA/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:45813:4826)

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 and the request ID.

This is a known issue. If Auto mode routes a request to a provider and that provider returns an error, Cursor won’t automatically switch to another one. Instead, it shows Provider Error.

Two workarounds:

  1. Resend the message. Auto mode will usually pick a different provider on retry.
  2. Pin a specific model instead of Auto, for example Sonnet 4.6 or GPT-5. This avoids the routing issue.

The team is aware of this. Let me know if the error keeps happening after you try these.