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

[Quas]

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.

PS!
Subscription/quota note (possible trigger)
My paid Cursor subscription quota is exhausted for the current month, so Cursor-hosted models are not available to me right now.
It’s possible this rerouting/interception bug only occurs when quota is exhausted, but I cannot verify until quota resets.

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.

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Cursor Version: 2.3.35
VSCode Version: 1.105.1
Commit: cf8353edc265f5e46b798bfb276861d0bf3bf120

For AI issues: add Request ID with privacy disabled

Request ID: d88b9d14-8605-471d-996e-3a54bda74a04
{“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}

Does this stop you from using Cursor

Yes - Cursor is unusable

[Colin]

Hey @Quas!

Thanks for reporting this. This is a known issue: when AWS Bedrock is configured, requests for non-Bedrock models are routed there as well. The team is aware of this issue, and I’ve added your report to increase visibility!

In the meantime, the workaround is to turn Bedrock off before using another model like Gemini.

[Quas]

Thanks for confirming, Colin. I saw one post, I believe, but it was not as detailed. And the issue was closed as well. Hopefully, it will be solved soon, thanks!