Opus 4.8 via Bedrock: "temperature" is deprecated for this model

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Same issue as Opus 4.7 via AWS Bedrock. Opus v4.8 is broken with this API Error:

The model returned the following errors: temperature is deprecated for this model.

Steps to Reproduce

Try to use Opus v4.8 via AWS Bedrock

Operating System

MacOS
Linux

Version Information

Version: 3.5.38
VSCode Version: 1.105.1
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750
Date: 2026-05-26T21:32:06.537Z
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: Darwin arm64 25.5.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @mjnowen Thanks for reporting, and I apologize for the inconvenience. This is a confirmed regression unfortunately. We fixed it with 4.7 but it has re-appeared with 4.8 We have a bug report raised for this and I’ll let you know when it is sorted out.

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

just like in 4.7: Opus 4.7 not functioning on Bedrock because of Temperature deprecation / 400 - #12.

switching to 4.7 works.

Steps to Reproduce

  1. use aws bedrock credentials
  2. enable us.anthropic.claude-opus-4-8
  3. try to send a request

Operating System

MacOS

Version Information

Version: 3.5.38
VSCode Version: 1.105.1
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750
Date: 2026-05-26T21:32:06.537Z
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: Darwin arm64 25.5.0

For AI issues: which model did you use?

us.anthropic.claude-opus-4-8

Does this stop you from using Cursor

No - Cursor works, but with this issue

Having same issue with opus-4-8

Hi @here We just merged a fix for this, you should see 4.8 requests going thru Bedrock successfully soon. Please give it a shot and let us know if all is well. This is a server-side change, so no client update is required (although we always encourage you to keep Cursor up to date!)

i see it works now.

Awesome! @Oguz_Akkas Thanks for confirming!

Yes, it works, but I also upgraded to Cursor v3.6.21 and now I have a new bug. Oh dear…

Ok thank you for highlighting! We’ve got a bug report open for this I’ll follow up on the other thread and let you know when any updates.