Skip to content

fix(sse): strip Codex temperature on native Responses passthrough - #12585

Open
fouadSalkini wants to merge 1 commit into
diegosouzapw:release/v3.8.51from
fouadSalkini:fix/codex-review-temperature-400
Open

fix(sse): strip Codex temperature on native Responses passthrough#12585
fouadSalkini wants to merge 1 commit into
diegosouzapw:release/v3.8.51from
fouadSalkini:fix/codex-review-temperature-400

Conversation

@fouadSalkini

@fouadSalkini fouadSalkini commented Sep 3, 2026

Copy link
Copy Markdown

Summary

  • Codex /responses (chatgpt.com) rejects sampling params with FastAPI {"detail":"Unsupported parameter: temperature"}. Combo codex-review forwarded client temperature/top_p onto gpt-5.6-sol-xhigh / gpt-5.6-luna-max because native Responses passthrough returns before the Responses allowlist.
  • Add a Codex STRIP_RULES entry and call stripUnsupportedParams("codex", …) in CodexExecutor.transformRequest next to the existing #3317 client-only field strip (user, prompt_cache_retention, safety_identifier).
  • Extend the #3317 passthrough test and stripUnsupportedParams unit tests so this cannot regress.

⚠️ base-red inherited: #12581

Test plan

  • node --import tsx/esm --test tests/unit/codex-responses-passthrough-strip-3317.test.ts tests/unit/executors-strip-unsupported-params.test.ts (28/28)
  • Retry a codex-review turn that previously 400'd on temperature (new Codex turn, not a 409-pinned retry)

Made with Cursor

Codex /responses rejects sampling params with FastAPI 400
Unsupported parameter: temperature. Native passthrough returned
before the Responses allowlist, so client temperature reached
upstream on combo traffic.

Co-authored-by: Cursor <cursoragent@cursor.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant