Codex App with gpt-5.6-sol aborts with unsupported prompt_cache_retention
What version of the Codex App are you using (From “About Codex” dialog)?
ChatGPT/Codex Desktop 26.814.41407, build 6720. Bundled app-server reports codex-cli 0.148.0-alpha.15.
What subscription do you have?
ChatGPT/Codex Desktop account. The local diagnostics do not expose the exact subscription tier. This is using the official OpenAI provider, not a custom/Azure provider.
What platform is your computer?
Darwin 25.5.0 arm64 arm
What issue are you seeing?
Codex Desktop repeatedly aborts GPT-5.6 Sol turns with:
{
"error": {
"message": "prompt_cache_retention is not supported on this model",
"type": "invalid_request_error",
"param": "prompt_cache_retention",
"code": "invalid_parameter"
}
}
This is happening with model gpt-5.6-sol in Codex Desktop using the official OpenAI provider. My local ~/.codex/config.toml does not set prompt_cache_retention or any prompt-cache override; it only sets the default model to gpt-5.6-sol.
The issue became frequent on 2026-08-19 after the Desktop app updated from build 6662 to build 6720 around 09:20 Asia/Shanghai time. The current bundled app-server is 0.148.0-alpha.15. I also observed one occurrence shortly before the app update while the old bundled runtime was still 0.148.0-alpha.9, so this may be a backend/client compatibility rollout issue rather than a purely local config problem.
Local evidence, sanitized:
- App version:
26.814.41407, build6720 - Bundled app-server:
codex-cli 0.148.0-alpha.15 - Previous app-server observed before update:
0.148.0-alpha.9 - Sparkle update event:
2026-08-19T01:20:02Z, current build before update was6662 - First same-day failure observed at
2026-08-19T01:04:13Z, before the app relaunched into0.148.0-alpha.15 - Additional failures observed after update at approximately
2026-08-19T01:53Z,02:15Z,02:32Z,02:44Z,02:52Z - Same error reproduced at both
xhighandhighreasoning effort, so changing reasoning effort does not appear to fix it.
This looks like a request-shape mismatch for GPT-5.6 models. The official OpenAI prompt caching docs say GPT-5.6 and later use prompt_cache_options.ttl, while earlier models use prompt_cache_retention:
https://developers.openai.com/api/docs/guides/prompt-caching
Related but not identical issues:
- #31882 is about Azure/custom providers and bundled model metadata. My repro is the official OpenAI provider in Codex Desktop.
- #32037 contains older logs showing
prompt_cache_retention: "24h"in a GPT-5.6 Sol response path, but that issue primarily tracks updater/app-server lifecycle behavior. This report is specifically about the unsupportedprompt_cache_retentioninvalid request error on official OpenAI-backed Codex Desktop.
What steps can reproduce the bug?
- Use Codex Desktop on macOS.
- Set/use model
gpt-5.6-sol. - Run a normal Codex task with a large existing context, especially after the 2026-08-19 Desktop update to build 6720.
- The turn can abort with
invalid_request_errorforparam: "prompt_cache_retention".
I do not currently have a minimal deterministic reproducer, but this has occurred repeatedly today across multiple local session rollouts.
What is the expected behavior?
Codex Desktop should not send, trigger, or route a GPT-5.6 Sol request using prompt_cache_retention if that field is unsupported for this model. It should use the GPT-5.6-compatible prompt-cache option shape, or disable the unsupported retention field for GPT-5.6-family models.
Additional information
This interrupted multiple paid/interactive Codex sessions and forced retries. Please investigate and ship a client or backend-side fix. I am also separately contacting support to request a usage/credit review for the failed runs.
39 Comments
Issue not limited to Sol, I have used Terra in Codex .deb app. Same issue happening after today's update.
Same issue here!!!ChatGPT/Codex Desktop 26.814.41407,V6720
Hello from Tokyo.
The same issue occurred with the ChatGPT app's Codex on Windows 11.
same issue
codex-cli 0.147.0
gpt-5.6-luna max
same
I tried codex-cli 0.148.0 and 0.147.0, both failed
gpt-5.6-sol max/ultra
same issue
Codex Desktop 26.814.41407 + GPT 5.6 Sol Medium Fast
same issue
same issue,it also happens to luna
same issue when I used gpt-5.6-sol.
same issue, chatgpt desktop: 26.818.11542, using 5.6 luna
same issue today
same issue with gpt 5.5
same issue
ChatGPT desktop 26.814.41407
using gpt-5.6-sol/gpt-5.5/gpt-5.3-codex-spark
same here with gpt-5.6-sol and gpt-5.6-luna.
same issue here
same issue here
same issue here
same issue
same issue
same issue
Looks like a world-wide issue. Maybe the team doesn't even test it before releasing update or just updating codex through codex and publishing, no manual review.
same issue
I agree
same issue
I believe we can reach out to Tibo via X and ask him to take a look at this issue
You simply need to provide the error message to Codex and instruct it not to pass
prompt_cache_retentionanymore; this will resolve the issue.<img width="418" height="296" alt="Image" src="https://github.com/user-attachments/assets/ac6b19a1-ea7c-47d6-b8c4-6d2ee84090d9" />
Tibo is busy in reset of usage at scheduled reset time.
Additional data point from macOS (ChatGPT Desktop 26.814.41407, bundled codex-cli 0.148.0-alpha.15):
The
gpt-5.5workaround suggested in #39397 did not work for me. Requests against gpt-5.5 reproduced the sameprompt_cache_retention is not supported on this modelerror, so switching models in the desktop app is not a reliable escape hatch.Failure pattern is consistent across every affected task:
invalid_request_errorTwo things that may help narrow this down:
config.tomldoes not contain this parameter.Running the same binary directly from the terminal (
/Applications/ChatGPT.app/Contents/Resources/codex), bypassing app-server, works fine with the same model and the same local config — including tool calls and web search.same wrong I met
same issue
https://github.com/Simpidbit/retrycodex/
Just retry, this project works
same, first time seen after todays windows app update.
Still occurs.
Same issue today
Same issue today
Same issue. 26.818.41509
started happening today after the update for me too, latest mac app sol max
same here started before the update, update hasnt fixed the problem
same happening to me