[BUG] OpenAI Compatible - Claude Opus 4.7 has `temperature` deprecated

[marty-a11y]

Problem (one or two sentences)

Any attempt to use claude-opus-4-7 through the OpenAI Compatible provider results in an error about temperature being deprecated.

Context (who is affected and when)

Happens all the time for every prompt in every scenario.

Reproduction steps

1. Set up OpenAI compatible with claude-opus-4-7
2. Send any prompt.

Expected result

No error from the API

Actual result

An error occurs

Variations tried (optional)

No response

App Version

3.52.1

API Provider (optional)

OpenAI Compatible

Model Used (optional)

claude-opus-4-7

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

Error: `OpenAI completion error: 400 litellm.BadRequestError: BedrockException - {\"message\":\"The model returned the following errors: {\\\"type\\\":\\\"error\\\",\\\"request_id\\\":\\\"req_p2msrdcxdgpww2tqhgwewtvomrkhc2l2pe5xdananom42vw6tqja\\\",\\\"error\\\":{\\\"type\\\":\\\"invalid_request_error\\\",\\\"message\\\":\\\"`temperature` is deprecated for this model.\\\"}}\"}`

[roomote-v0]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause

The OpenAiHandler (used for the "OpenAI Compatible" provider) always sends the temperature parameter in API requests without checking the supportsTemperature field from ModelInfo. When proxying to Claude Opus 4.7 via a gateway like LiteLLM/Bedrock, this causes a 400 BadRequestError because that model has deprecated temperature.

Other providers like openai-native and gemini already correctly check supportsTemperature !== false before including temperature in requests. The ModelInfo type already has a supportsTemperature field (defined in packages/types/src/model.ts) -- it just isn't checked in the OpenAI Compatible code path.

Proposed Changes

1. src/api/providers/openai.ts (OpenAiHandler) - In createMessage() (line ~157): wrap the temperature field with a modelInfo.supportsTemperature !== false check, so it's omitted when the model doesn't support it. Same for completePrompt().

2. src/api/transform/model-params.ts (getModelParams) - In the "openai" format branch: add a check for model.supportsTemperature === false to set params.temperature = undefined, generalizing the existing special-cases for o1/o3-mini. This fulfills the existing TODO at line 157.

3. webview-ui/src/components/settings/providers/OpenAICompatible.tsx - Add a "Supports Temperature" checkbox (similar to the existing "Supports Images" and "Supports Prompt Caching" toggles) so users can explicitly mark models that don't support temperature. This lets users configure supportsTemperature: false in their openAiCustomModelInfo.

4. src/api/providers/openai-compatible.ts (OpenAICompatibleHandler) - In createMessage() (line ~173) and completePrompt() (line ~207): add the same supportsTemperature !== false guard, since this base class is used by MoonshotHandler and may be extended by future providers.

5. src/api/providers/base-openai-compatible-provider.ts - In createStream() (line ~87): add the same guard, since this base class is used by several providers (SambaNova, Fireworks, ZAI, Roo, Baseten).

6. Tests - Add test coverage for the temperature suppression behavior in the affected providers.

This approach is consistent with how openai-native.ts and gemini.ts already handle it, and gives OpenAI Compatible users the ability to opt out of temperature for models that require it.

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[yuvarajl]

@roomote go ahead and raise an PR

[roomote-v0]

I've seen your comment and will proceed with the implementation. I'll open a PR to share progress shortly.

[roomote-v0]

Opened PR #12164 with my attempt at addressing this. The fix omits the temperature parameter when supportsTemperature is false in the model info, and adds a "Supports Temperature" checkbox in the OpenAI Compatible settings UI so users can toggle it off for models like Claude Opus 4.7. Feedback welcome!