Unable to reach the model provider in auto mode but manually selecting a model works

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Unable to reach the model provider in auto mode but manually selecting a model works

Request ID: 89ce318d-1249-4f2d-a927-7c365dd89683
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
mie: [resource_exhausted] Error
at P5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23755)
at B5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at $5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at Wou.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async $Oa.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46832:10024)
at async n5u.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46886:9277)
at async n5u.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46886:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
at async Ea (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45811:4826)

Yes I can use the claude or any model, but Auto mode is used as a cost efficient measure and this bug is burning through my credits.

Steps to Reproduce

Pretty much selecting the auto mode can produce this error

Screenshots / Screen Recordings

Screenshot 2026-03-18 at 11.42.46.png
Screenshot 2026-03-18 at 11.42.46.png767×1440 25.2 KB

Operating System

MacOS

Version Information

Version: 2.6.19
VSCode Version: 1.105.1
Commit: 224838f96445be37e3db643a163a817c15b36060
Date: 2026-03-12T04:07:27.435Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Auto

For AI issues: add Request ID with privacy disabled

Request ID: 89ce318d-1249-4f2d-a927-7c365dd89683
{“error”:“ERROR_RESOURCE_EXHAUSTED”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
mie: [resource_exhausted] Error
at P5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:23755)
at B5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34267:22658)
at $5A (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:6285)
at Wou.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34268:10400)
at async $Oa.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46832:10024)
at async n5u.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46886:9277)
at async n5u.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:46886:13663)
at async bMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:34329:17597)
at async Ea (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:45811:4826)

Additional Information

This is burning my credits as i have to use a premium model

Does this stop you from using Cursor

No - Cursor works, but with this issue

3

I encountered the same problem

5

me2，but change the model without auto，its working

6

Me too. When will it be fixed?

7

It’s working now.

8

Yes, suddenly started working. But this is annoying :frowning:

9

Hey everyone, this is a known issue with Auto mode. Sometimes it routes a request to a provider that’s currently overloaded and doesn’t switch to another one automatically. Manually picking a model skips that logic, so it works fine.

The team is aware. There’s no ETA for a fix yet, but your report helps us prioritize it.

For now, the workaround is to pick a model manually instead of Auto. This won’t use more credits as long as you choose a non-premium model, like composer-1.5 or gemini-2.5-flash.

Looks like it’s working again now, but if it happens again, just switch to a specific model.

1 Like