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.