AUTO mode fails repeatably

[Ruan_Klopper]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Keeps getting “We’re having trouble connecting to the model provider” issue on auto mode

Steps to Reproduce

By using the AI agent

Expected Behavior

Model is not supposed to rate limit me, nor fail

Screenshots / Screen Recordings

Operating System

Other

Version Information

Version: 3.20.10
VS Code Extension API: 1.128.0
Commit: d6f462cdd0a6a6d1cff570daf980e671d0a63de0
Date: 2026-09-10T21:04:54.045Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 42.10.0
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

For AI issues: which model did you use?

Auto & Composer

For AI issues: add Request ID with privacy disabled

Request ID: 38773895-96aa-4984-ba56-7db3e36fbb34
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:true,“additionalInfo”:{“providerStatusCode”:“503”},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
RetriableError: [resource_exhausted] Error
at z6f (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8346:137535)
at Pto (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8346:135961)
at g4f (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8347:13639)
at Object.classify (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8347:17861)
at l4f (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8347:5924)
at async Gto.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8347:17168)
at async Cle.resume (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8447:35550)
at async rBo.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:17887:16374)
at async rBo.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:17887:37100)
at async CDe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8425:4549)

Does this stop you from using Cursor

Yes - Cursor is unusable

[deanrie]

Hey, thanks for the detailed report and the Request ID.

This is an issue on our side that’s currently affecting some Auto requests, and it matches your Request ID. It’s not related to your network or setup, and it’s not a rate limit issue, so you don’t need to fix anything on your end. We’re already looking into it.

While this is being fixed, the workaround is to pick a specific model in the model picker instead of Auto, for example Composer 2.5 or one of the named Grok models. With a selected model, requests should go through normally.

Once this is fixed, Auto should start working again on its own, and you won’t need to change anything. If you still see the error after switching to a specific model, send a new Request ID and we’ll take another look.