reasoning.summary not supported with gpt-5.3-codex-spark
Open 💬 3 comments Opened Jun 5, 2026 by coalio
💡 Likely answer: A maintainer (etraut-openai, contributor)
responded on this thread — see the highlighted reply below.
What version of Codex CLI is running?
0.137.0
What subscription do you have?
Pro
Which model were you using?
gpt-5.3.codex-spark
What platform is your computer?
Linux 6.6.87.2-microsoft-standard-WSL2 x86_64 x86_64
What terminal emulator and version are you using (if applicable)?
Neovide
Codex doctor report
What issue are you seeing?
reasoning.summary crashes on models that don't support it or use the older apis
Uploaded thread: 019e98e5-0eeb-70d1-b905-6173572a883c
What steps can reproduce the bug?
Uploaded thread: 019e98e5-0eeb-70d1-b905-6173572a883c
What is the expected behavior?
_No response_
Additional information
_No response_
3 Comments
When you say that it "crashes", do you mean that the harness terminates? Or do you mean that an error is reported to the user when this condition occurs? If it's the latter, then that's the expected behavior.
@etraut-openai The harness doesn't terminate (as in the CLI exiting), but the user gets the raw API JSON error response, I don't believe this is intended except for the error being surfaced. There's a bad parameter being sent from the harness side.
Notifying the user that reasoning summaries will be disabled as they're unsupported by the model would be ideal
<img width="964" height="968" alt="Image" src="https://github.com/user-attachments/assets/9b50255f-40b0-4688-8406-ad0353658ec1" />
Note for maintainers: The automated triage run by @ctkm-aelf (FKST-codex-harness#114) improperly marked this issue as
needs-infoand closed the saga tracking.The reproduction runner collapsed due to a host-level compilation error (
ENOSPC/ out of disk space) while buildingcodex-core, meaning the test never actually ran. The underlying payload gating failure regardingreasoning.summaryincodex-rs/core/src/client.rs:790is valid and has not been evaluated.The systemic class-wide leak where runner infrastructure falls back to
needs-infoclassification is being tracked at ChronoAIProject/fkst-packages#2168.