Mb
July 16, 2026, 12:58pm
1
The ‘gpt-5.6-sol’ model requires a newer version of Codex. Please upgrade to the latest app or CLI and try again.
=> Despite being on the latest version.
Trying to check if it works under Pre-Release.
EricGT
July 16, 2026, 1:08pm
2
You are welcome to discuss Codex issues on the forum, however the official place to report and track them is the GitHub issue tracker for OpenAI Codex .
I had ChatGPT look for the closest related issue and it identified:
opened 05:42PM - 09 Jul 26 UTC
bug
### What version of Codex CLI is running?
codex-cli 0.143.0
### What subscript… ion do you have?
NVIDIA
### Which model were you using?
gpt-5.6-sol
### What platform is your computer?
_No response_
### What terminal emulator and version are you using (if applicable)?
_No response_
### Codex doctor report
```json
```
### What issue are you seeing?
⚠ Model metadata for `gpt-5.6-sol` not found. Defaulting to fallback metadata; this can degrade performance and cause issues.
⚠ Falling back from WebSockets to HTTPS transport. stream disconnected before completion: websocket closed by
server before response.completed
■ Error running remote compact task: {"detail":"The 'gpt-5.6-sol' model requires a newer version of Codex. Please
upgrade to the latest app or CLI and try again."}
Token usage: __
To continue this session, run codex resume 019f244a-489a-7482-803e-1644660fafb7
[10:39:38] radwankar@DJQTT9QWYL ___ % brew update codex
Warning: Use `brew upgrade codex` to upgrade formulae; running it instead.
Warning: Not upgrading codex, the latest version is already installed
### What steps can reproduce the bug?
Resume a conversation when previously using gpt-5.6-sol.
### What is the expected behavior?
_No response_
### Additional information
_No response_
If that issue matches your problem, consider adding a
If it is not the same issue, try searching the existing GitHub issues for a closer match. If you cannot find one, then open a new issue with as much detail as possible.
Mb
July 16, 2026, 1:12pm
3
Thanks for the info. I will try. Considering you had the “bug” flag here; I assumed
EricGT
July 16, 2026, 1:15pm
4
No worries, that is why we are here.
Hope you reach a successful resolution.
reaction on the GitHub issue page itself, not just on the forum topic, as reactions on GitHub help the developers gauge impact and prioritize work.