Consistently Getting "We're having trouble connecting to the model provider. This might be temporary - please try again in a moment."

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have been getting the mentioned error repeatedly the last couple of days.

“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”

When this happens, I am not able to make any requests for an extended period of time. I was unable to use Cursor at all last night. It worked for a short time earlier this afternoon, then started giving the error again.

Here is the most recent ID received:

Request ID: 55f2029d-9fa2-47b4-8bba-a996cb43660a
{“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”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
aBi: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at Pnw (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:43963:24394)
at Bnw (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:43963:23385)
at $nw (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:43964:6487)
at v9u.run (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:43964:11286)
at async JIn.runAgentLoop (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:56307:11753)
at async C0d.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:56377:11057)
at async C0d.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:56377:17161)
at async ZOe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:44075:19892)
at async Gl (vscode-file://vscode-app/c:/Users/…/workbench.desktop.main.js:55360:4891)

Steps to Reproduce

It happens intermittently when sending request in agent or ask modes.

Expected Behavior

Not get an error

Screenshots / Screen Recordings

Operating System

Windows 10/11

Version Information

Version: 3.0.13 (user setup)
VSCode Version: 1.105.1
Commit: 48a15759f53cd5fc9b5c20936ad7d79847d914b0
Date: 2026-04-07T03:05:17.114Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Sonnet 4.6
Opus 4.6
Composer 2 Fast
Codex 5.3
GPT-5.4
Premium

For AI issues: add Request ID with privacy disabled

Request ID: 55f2029d-9fa2-47b4-8bba-a996cb43660a
{“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”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
aBi: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at Pnw (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43963:24394)
at Bnw (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43963:23385)
at $nw (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43964:6487)
at v9u.run (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43964:11286)
at async JIn.runAgentLoop (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56307:11753)
at async C0d.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:11057)
at async C0d.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:17161)
at async ZOe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44075:19892)
at async Gl (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55360:4891)

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Just sending the word “test”, I got the following just now:

Request ID: d0c6bb32-c561-433b-b43e-f497996496ec
{“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”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
aBi: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at Pnw (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43963:24394)
at Bnw (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43963:23385)
at $nw (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43964:6487)
at v9u.run (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:43964:11286)
at async JIn.runAgentLoop (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56307:11753)
at async C0d.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:11057)
at async C0d.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:56377:17161)
at async ZOe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:44075:19892)
at async Gl (vscode-file://vscode-app/c:/Users/kevin/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:55360:4891)

Hey, thanks for the detailed report with Request IDs and stack traces.

This is a known issue on our side. One of our model providers is having an outage, and it’s affecting multiple models at once. It’s not related to your network or setup.

The team is aware. For now, as a workaround, if a specific model errors out, try switching to a different model and resend the request. Based on our server logs, some models are more stable than others right now.

I’ll post an update here when we have more info. Sorry for the trouble.

1 Like

Thank you for the quick update, I appreciate it!