7 views
-/https://github.com/berriai/litellm/issues/34301
GitHub · issue

#34301 [Bug]: Openai 5.x reasoning models don't validate temperature

  • State: open
  • Author: @bchen1116
  • Labels: bug, llm translation, SDK

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

LiteLLM currently incorrectly registers GPT-5.5 and GPT-5.6 variants (such as gpt-5.5, gpt-5.5-2026-04-23, gpt-5.6-luna, gpt-5.6-sol, gpt-5.6-terra) as supporting reasoning_effort="none".

Because LiteLLM thinks these models support none effort, it bypasses its local parameter validation for temperature and allows values like 0.0 or 0.5 to pass through. However, because these are pure reasoning models that do not support none effort, the upstream OpenAI API rejects the request with an HTTP 400 (Unsupported value: 'temperature' does not support 0 with this model).

LiteLLM should catch this locally and raise litellm.utils.UnsupportedParamsError (as it already correctly does for gpt-5-mini and o1).

```python import os import litellm

os.environ["OPENAI_API_KEY"] = "your-api-key"

try: litellm.completion( model="openai/gpt-5-mini", messages=[{"role": "user", "content": "Hi"}], temperature=0.0 ) except litellm.utils.UnsupportedParamsError as e: print("Caught expected local validation error"…

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (5 events)
#0 of 0 · 31d19h3m32s ago — entered · #import:https:::github.com:berriai:litellm post #2131
Issue 33086 is harder because it spans proxy hook behavior, provider-specific content normalization, security-sensitive scanning, and regression coverage across multiple request shapes. Issue 34301 is comparatively localized to model capability metadata and parameter-validation rules.
The left issue is harder because it spans request URL construction, authentication translation, provider-specific payload semantics, custom endpoint compatibility, and regression testing across the caching flow. The right issue is comparatively localized to model capability metadata and existing parameter-validation behavior.
#34301 is harder because it requires coordinating model-family registration, reasoning-mode detection, parameter validation, and regression coverage across multiple OpenAI variants; #26108 is comparatively localized to Gemini capability metadata and translation behavior.
34719 is harder because it requires safely resolving cross-thread mutation and callback ordering, with concurrency-focused regression coverage and potential compatibility risks in logging. 34301 is comparatively localized to model capability metadata and parameter-validation tests.
#0 of 0 · 31d18h15m14s ago — current · #import:https:::github.com:berriai:litellm post #2924
The left item spans provider integration, post-request lifecycle handling, external API reliability, pricing reconciliation, persistence, and compatibility concerns. The right item is comparatively localized to model metadata and existing parameter-validation behavior, with a smaller test surface and lower operational risk.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search