Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
When I submit a prompt in Cursor, the request fails with the following message:
“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”
The error prevents the Agent from completing the request. Although the message suggests that the issue may be temporary, the error details report “isRetryable”: false, and the stack trace shows a NonRetriableError.
Error details:
- Error code: ERROR_PROVIDER_ERROR
- Error title: Provider Error
- Provider status code: 400
- isRetryable: false
- isExpected: true
The stack trace includes wfo._executeTurn, Sue.runAgentLoop, and BWo.streamFromAgentBackend.
Please investigate why the request is failing and whether the error message can provide a more specific explanation of the underlying issue.
Request ID: 4d322798-3778-4e53-b8a5-68c6e0eb7400
{“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”:{“providerStatusCode”:“400”},“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.
NonRetriableError: Provider Error We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
at Kyv (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8788:119304)
at wfo._executeTurn (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8788:138652)
at async wfo.executeTurn (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8788:127663)
at async Sue.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8782:31619)
at async BWo.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:18542:21034)
at async BWo.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:18542:44293)
at async uMe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8755:4574)
at async uMe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:8750:74385)
at async Hc (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:17529:87733)
Steps to Reproduce
- Open Cursor.
- Open an Agent chat.
- Enter a prompt and submit it.
- Observe that the request fails with a “Provider Error” and the message: “We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”
The attached error details show ERROR_PROVIDER_ERROR with providerStatusCode “400”.
Expected Behavior
Cursor should submit the prompt successfully and return a response from the selected model.
If the request cannot be processed, Cursor should display a clear, actionable error explaining the reason for the failure, rather than a generic connection error suggesting a temporary issue.
Operating System
MacOS
Version Information
Version: 3.23.12
VS Code Extension API: 1.128.0
Commit: 2d29876d567da1607532b23bbf2cd5ddbca496f0
Date: 2026-10-01T04:41:16.627Z
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.5.0
For AI issues: which model did you use?
Composer 2.5
For AI issues: add Request ID with privacy disabled
Request ID: 4d322798-3778-4e53-b8a5-68c6e0eb7400
Does this stop you from using Cursor
Yes - Cursor is unusable