Problems encountered when connecting to the model provider

[zhang_kevin]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This issue kept occurring when executing complex tasks.

Steps to Reproduce

Please see requestID.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.4.16 (Universal)
VSCode Version: 1.105.1
Commit: f736016b0aa20ba1f99b7eec1dda48579fa4c290
Date: 2026-05-13T16:57:36.546Z
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: Darwin x64 24.5.0

For AI issues: which model did you use?

Opus 4.7

For AI issues: add Request ID with privacy disabled

Request ID: 325eedfd-99a5-4072-aa18-91472691a391
{“error”:“ERROR_NETWORK_ERROR”,“details”:{“title”:“Network Error”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“isRetryable”:true,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[resource_exhausted] Error
IAe: [resource_exhausted] Error
at _m0 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29834:25583)
at ym0 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29834:24382)
at Am0 (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29835:6490)
at jCp.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29835:11286)
at async nks.resume (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:42179:22473)
at async nlf.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:42247:12673)
at async nlf.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:42247:19902)
at async fSt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29950:17236)

Does this stop you from using Cursor

Yes - Cursor is unusable

[kevinn (Kevin Neilson)]

Hi @zhang_kevin — sorry about the trouble here.

This looks related to an active incident affecting Opus 4.6 and Opus 4.7. We’re investigating elevated error rates from the provider and monitoring here: https://status.cursor.com/

Try another model in the meantime!

[zhang_kevin]

Hi team,

I am writing to follow up on my initial report above regarding the frequent Opus 4.7 timeout issues experienced yesterday.

As a premium Ultra subscriber, this prolonged service instability severely disrupted my development workflow and caused significant project delays. During the outage, many complex tasks consumed my usage credits but ultimately failed to execute successfully. This forced me to frequently retry the prompts, which further drained my credits without delivering any results.

Given that the service was completely unusable while continuing to deduct my quota, I would like to formally request compensation, such as a credit adjustment to add extra Fast / Ultra requests.

Could someone from the team please investigate this matter and assist with my account credit adjustment?

Thanks,
Kevin

[kevinn (Kevin Neilson)]

Sent DM