Bedrock enabled reroutes Gemini API requests to Bedrock (“Selected model is not supported by bedrock”) — cannot use Gemini + Bedrock simultaneously

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I have both AWS Bedrock (Anthropic) and Google Gemini API key configured/enabled in Cursor.

When I select a Gemini model in Cursor Chat (e.g., Gemini 3 Pro), Cursor does not appear to call Google/Gemini; instead it behaves as if the request is being sent to AWS Bedrock, returning a Bedrock error that the selected model is not supported by Bedrock.

This same behavior also seems to affect other non‑Bedrock models (e.g., Opus 4.5, Composer), which also return “Selected model is not supported by bedrock…” errors while Bedrock is enabled.

Steps to Reproduce

Settings → Models: enable/configure AWS Bedrock (Anthropic via Bedrock).

Settings → Models: enable/configure Google Gemini API key (Gemini API, not Vertex).

Open Chat → select Gemini 3 Pro (also reproduced with Opus 4.5 / Composer).

Send any prompt.

Expected Behavior

If a Gemini model is selected, Cursor should call the Gemini API key provider and not AWS Bedrock.

Bedrock should only be used for Bedrock model IDs, and enabling Bedrock should not “intercept” or reroute other providers’ models.

It should be possible to have Bedrock + Gemini configured at the same time and use each by selecting the corresponding model.

Operating System

MacOS

Version Information

Version: 2.5.26 (Universal)
VSCode Version: 1.105.1
Commit: 7d96c2a03bb088ad367615e9da1a3fe20fbbc6a0
Date: 2026-02-26T04:57:56.825Z
Build Type: Stable
Release Track: Default
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

For AI issues: add Request ID with privacy disabled

Request ID: e4f3f8b2-d6ce-479a-8d75-778dc5968642
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We encountered an issue when using your API key: Selected model is not supported by bedrock, please use a different model\n\nAPI Error:\n\n\nSelected model is not supported by bedrock, please use a different model\n”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[invalid_argument] Error
_he: [invalid_argument] Error
at jpA (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32115:44883)
at WpA (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32115:43786)
at ZpA (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32116:5088)
at Ool.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32116:9098)
at async s$o.resume (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44360:12816)
at async zOl.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:8884)
at async zOl.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:44408:9837)
at async yLe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:32182:15752)
at async Gs (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:43415:4781)

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this is a known regression in 2.5.26. The original fix in 2.5 didn’t cover every case. AWS Bedrock is still intercepting requests to non-Bedrock models like Gemini, Codex, and others. Multiple users are running into this.

There’s also a related thread with more context: Cursor + AWS Bedrock: can we use both without constantly switching settings?

The team is aware. There’s no ETA for a fix yet, but your report helps us prioritize it.

For now, the workaround is the same as before. Turn Bedrock off in Settings > Models > API Keys > AWS Bedrock before you use non-Bedrock models. I know it’s tedious, but it’s the only reliable option right now.