litellm/litellm/responses
ryan-crabbe-berri 0c83e831db fix(responses): carry the reasoning summary as an alias, not inside reasoning_effort
The bridge probe asked `responses_api_bridge_check` with the summary read straight off
the Responses object, but `litellm.completion` reads it from `optional_params` via
`peek_reasoning_summary_aliases`, which the bridged request never populated. So gpt-5,
gpt-5.1 and azure/gpt-5 answered "bridging" to the probe and "not bridging" for real,
and the object still landed on Chat Completions, which only takes a string

`reasoning_effort` is now always the effort string, and `summary` rides the
`reasoning_summary` alias that main.py already reassembles into `{effort, summary}` on
the bridged path. The alias is emitted only when the probe says the model bridges, so
no chat provider ever sees it, and the probe is now asked with the exact params this
transform emits
2026-09-12 17:49:30 -07:00
..
file_search fix(file_search): escape the dropped vector_store_id in the warning 2026-09-05 16:44:54 -07:00
litellm_completion_transformation fix(responses): carry the reasoning summary as an alias, not inside reasoning_effort 2026-09-12 17:49:30 -07:00
mcp merge: bring litellm_internal_staging into litellm_fix_agent_mcp_grants 2026-09-07 16:35:40 -07:00
main.py fix(router): honor Codex reminders and map classifier failures 2026-09-10 13:48:21 -07:00
sse_output_recovery.py refactor(repositories): type prisma table access with one generic protocol 2026-08-25 12:14:17 +00:00
streaming_iterator.py fix(responses): keep the client's usage shape when the logging copy cannot re-validate the response 2026-09-09 16:31:48 -07:00
utils.py fix(router): strip encrypted reasoning on an auto-router tier change instead of a 503 (#40280) 2026-09-09 11:04:11 -07:00