When sending 3 or more consecutive chats in Auto mode, Cursor throws a Provider Error with the message: “We’re having trouble finding the resource you requested.”
The error is marked as non-retryable (isRetryable: false).
Hey, thanks for the report with the request ID. That helps.
This is a known issue with Auto mode. When Auto picks a provider and that provider temporarily returns an error (404), the system doesn’t switch to another provider and shows Provider Error instead of retrying automatically. The team is aware of this.
For now, there are two workarounds:
Retry: just send the message again, Auto mode will usually route it to another provider.
Pin a specific model: instead of Auto, pick a specific model. This avoids the routing issue.
Let me know if you still see the error after pinning a model.
Request ID: 34c2616f-c754-4630-a410-3b08d197e8fb
{“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/shett/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23670)
at h9A (vscode-file://vscode-app/c:/Users/shett/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at w9A (vscode-file://vscode-app/c:/Users/shett/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at rau.run (vscode-file://vscode-app/c:/Users/shett/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/shett/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/shett/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/shett/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/shett/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
Steps to Reproduce
this appeared in between the prompt and then stopped the agent from working
I have tried creating a new chat and testing it two or three times. After about 15 minutes, it returned to normal. U should try again because it occasionally glitches. This method works well for me, but if u run multiple chats simultaneously, there is a high probability it will fail again. I currently dont have any other workaround.
