Cursor doesn't work for a week more

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

We’re having trouble finding the resource you requested. If the problem persists, please contact support.
Request ID: e1ef7930-c237-4203-b750-223b6179f10e
{“error”:“ERROR_PROVIDER_ERROR”,“details”:{“title”:“Provider Error”,“detail”:“We’re having trouble finding the resource you requested. If the problem persists, please contact support.”,“isRetryable”:false,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
Cvs: Provider Error We’re having trouble finding the resource you requested. If the problem persists, please contact support.
at Pf_ (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:24260)
at Rf_ (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29432:23144)
at Uf_ (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:6490)
at q0h.run (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29433:11307)
at async cQi.runAgentLoop (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41748:12418)
at async Vnm.streamFromAgentBackend (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:12344)
at async Vnm.getAgentStreamResponse (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:41816:19567)
at async lCt.submitChatMaybeAbortCurrent (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:29548:16906)
at async Va (vscode-file://vscode-app/d:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:40804:4230)

Steps to Reproduce

cannot use cursor anymore

Expected Behavior

every time notes like this

Operating System

Windows 10/11

Version Information

Version: 3.2.11 (user setup)
VSCode Version: 1.105.1
Commit: e9ee1339915a927dfb2df4a836dd9c8337e17cc0
Date: 2026-04-24T14:36:47.933Z
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.19045

Does this stop you from using Cursor

Yes - Cursor is unusable

5

Hey, thanks for the report. This is a known regression with Gemini 3.x BYOK keys gemini-3-flash, gemini-3-pro, gemini-3.1-pro. After the Cursor client update, Cursor sends the wrong model name to Google AI Studio, so the response comes back as a 404. We’re tracking it and working on a fix, but I can’t share an exact ETA yet.

Workaround for now:

  • Use gemini-2.5-flash with your BYOK key. The slug is valid there and requests work.
  • Or disable your Google API key and switch to Cursor default models Sonnet, GPT-5, etc. Those go through our infra and work.

Related thread with the same issue, you can follow it for updates: Gemini API key not working in Cursor, getting PROVIDER_ERROR

Once it’s fixed, I’ll post here.