Bedrock interferes with Google/Gemini model requests when both providers are configured

[nirrenn]

Describe the Bug

Bedrock interferes with Google/Gemini model requests when both providers are configured.

Steps to Reproduce

1 - Configure AWS Bedrock credentials in Settings > Models
2 - Also configure a Google API key in Settings > Models
3 - Select a Gemini model in the model picker
4 - Send a chat request

Expected Behavior

Request routes through Google’s API using the Gemini model

Operating System

MacOS

Version Information

Version: 2.6.18
VSCode Version: 1.105.1
Commit: 68fbec5aed9da587d1c6a64172792f505bafa250
Date: 2026-03-10T02:01:17.430Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin x64 24.6.0

Additional Information

We encountered an issue when using your API key: Selected model is not supported by bedrock, please use a different model

API Error:

Selected model is not supported by bedrock, please use a different model

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[deanrie]

Hey, this is a known bug. Bedrock intercepts requests to all models when its credentials are set, even if a non-Bedrock model is selected. There was an attempt to fix it in 2.5, but the regression came back.

The same bug is discussed here: Bedrock enabled reroutes Gemini API requests to Bedrock (“Selected model is not supported by bedrock”) — cannot use Gemini + Bedrock simultaneously

The only working workaround right now is to disable Bedrock in Settings > Models > API Keys > AWS Bedrock before using Gemini. It’s annoying, but there aren’t any other options yet.

The team is aware. There’s no timeline for a fix yet, but your report helps with prioritization, especially since the bug has carried across multiple versions.