Hi Cursor Support,
Only Claude fails in Cursor. GPT and Codex work normally in the same Cursor client, same account, and same network.
When I use Claude Code / Claude model, even a simple “hi” prompt fails with:
“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”
I am using Cursor’s included usage, not my own Anthropic API key.
Please help check whether my account, region, quota, or Claude/Anthropic provider routing is affected.
For AI issues: add Request ID with privacy disabled
Request ID: 8cf20d33-2139-43b9-aea5-477faa9cfe65
{“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
EEe: [resource_exhausted] Error
at LJy (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29226:25504)
at DJy (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29226:24303)
at qJy (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29227:6490)
at c5d.run (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29227:11311)
at async vfs.runAgentLoop (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41560:14333)
at async jCh.streamFromAgentBackend (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:12259)
at async jCh.getAgentStreamResponse (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41628:19379)
at async Qbt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29342:17002)
at async yd (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40612:4226)
This is most likely due to regional restrictions on certain models. Your account and usage quota are both fine. Using Auto mode automatically selects the best available model for your situation and routes around any restrictions.
To help narrow this down, could you try two things?
Run a Network Diagnostic: Go to Cursor Settings > Network and click Run Diagnostics, then share the results (there’s a “Copy diagnostics” button). This will tell us if there’s a connectivity issue between your machine and our model endpoints.
Try Claude again and share a fresh Request ID: Open a new chat, select Claude, send a short message like “hi”. If it fails, click the three dots at the top right of the chat and select Copy Request ID, then paste it here.
[Request ID: 5e7cb49b-558e-42c7-9cb4-787f7ccefd3b
{“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
REe: [resource_exhausted] Error
at cHy (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29320:25583)
at aHy (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29320:24382)
at gHy (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29321:6490)
at D5d.run (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29321:11311)
at async Pfs.runAgentLoop (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41654:14477)
at async kkh.streamFromAgentBackend (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41722:12518)
at async kkh.getAgentStreamResponse (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41722:19638)
at async eyt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29436:17002)
at async Hl (vscode-file://vscode-app/d:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40709:4226)]
Thanks for the request ID! I’ve confirmed the issue is still active — your Claude requests are failing before reaching any model provider on our end.
I’m escalating this to our engineering team. They’ll need to look at why direct Claude routing isn’t working for your account specifically (since Claude via Auto mode through an alternate path does work for you).
In the meantime, Auto mode should continue working for Claude-class tasks — it routes through a path that succeeds for your account. You can select it from the model picker.
I’ll follow up here once the team has a resolution.
Hi,
I have been experiencing persistent network connection issues this afternoon. Below is the error request log. I am currently using opus4.7. Could you please look into this and help me identify what the problem is?
Request ID: 11d44032-4055-4052-a8eb-fddc4a25f874 {“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)
Thanks for the report. Looking at the backend data for your request, this appears to be a different issue from what this thread tracks. The OP’s issue is a persistent routing failure where Claude never reaches the provider at all. Your error is an intermittent upstream connectivity issue where Claude is working most of the time but occasionally hitting transient failures.
The good news: your account data shows Claude requests succeeding normally as of May 15-16. If you’re still seeing errors, could you create a new thread with:
A fresh Request ID from a failing attempt
Your Network Diagnostics results (Cursor Settings > Network > Run Diagnostics > Copy diagnostics)
That way we can investigate your specific issue properly if it recurs.