Opus 4.7 not functioning on Bedrock because of Temperature deprecation / 400

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When using Bedrock, we get a 400, which makes sense:

point 2 specifies that temp is no longer supported :slight_smile:

Awesome that you got it live so quickly in cursor!

Steps to Reproduce

Use Bedrock and pick opus 4.7

Expected Behavior

works - but get The model returned the following errors: {“type”:“error”,“request_id”:“req_yzla6oko5h7iozhy5femfe3q2vv27ximde3h5ejxpqhro7cewjwa”,“error”:{“type”:“invalid_request_error”,“message”:“temperature is deprecated for this model.”}}
instead

Operating System

MacOS

Version Information

Version: 3.2.0-pre.32.patch.0
VSCode Version: 1.105.1
Commit: a35c6137b003856e0beea5591910c649f5e97350
Date: 2026-04-16T05:58:50.114Z
Layout: editor
Build Type: Stable
Release Track: Nightly
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

Opus 4.7

For AI issues: add Request ID with privacy disabled

Request ID: ec33e668-e0d5-41a7-a371-96e6b5c69f1a
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We encountered an issue when using your API key: Provider was unable to process your request\n\nAPI Error:\n\n\nThe model returned the following errors: {\"type\":\"error\",\"request_id\":\"req_yzla6oko5h7iozhy5femfe3q2vv27ximde3h5ejxpqhro7cewjwa\",\"error\":{\"type\":\"invalid_request_error\",\"message\":\"`temperature` is deprecated for this model.\"}}\n”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:true}
[invalid_argument] Error
hae: [invalid_argument] Error
at orw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29196:24629)
at rrw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29196:23431)
at mrw (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29197:6487)
at gWu.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29197:11285)
at async YPn.resume (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41516:16087)
at async hRd.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41584:12293)
at async hRd.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:41584:18686)
at async h5e.submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:29310:16837)

Additional Information

see error in request id field

Does this stop you from using Cursor

No - Cursor works, but with this issue

3 Likes

Hey, thanks for the report and for linking the migration guide, that confirms it.

This is a bug on our side. We’re still sending the temperature parameter for Opus 4.7 on Bedrock, and that model no longer accepts it. I’ve flagged this with the team. No ETA yet, but your report helps us prioritize it.

I’ll update here when there’s news.

+1 on this. Our team has to hard switch to Claude Code to try the new model. Would really appreciate a quick fix!

fwiw: the docs claim that model still accepts the params if they are set to the default values

This should be fixed now!