›_ Codex Issues
Codex Issues / #32034

My CodeX CLI does not have the GPT5.6 model.

Open 💬 3 comments Opened Jul 10, 2026 by zwl00000
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

What version of Codex CLI is running?

v0.144.1

What subscription do you have?

team

Which model were you using?

gpt5.5

What platform is your computer?

ubuntu24.04

What terminal emulator and version are you using (if applicable)?

ubuntu Terminal

Codex doctor report

What issue are you seeing?

<img width="2120" height="634" alt="Image" src="https://github.com/user-attachments/assets/834e5fc4-ea65-4fa8-a940-7fce55605b2d" />

What steps can reproduce the bug?

Uploaded thread: 019f4a7c-92da-7342-8cba-fb5745a9a5bd

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

3 Comments

github-actions[bot] contributor · 1 month ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #31873
  • #31869
  • #31905

Powered by Codex Action

ishassan · 1 month ago

Reproduced on Amazon Linux/EC2 with Codex CLI 0.144.1.

I can use GPT-5.6 on my local mac app, Codex CLI on mac, on web, on iPhone. The only missing interface is Codex CLI on Amazon Linux/EC2.

A complete removal and clean standalone reinstall did not resolve it. Explicitly running codex --model gpt-5.6-sol returns: “The 'gpt-5.6-sol' model requires a newer version of Codex.”

ishassan · 1 month ago

I managed to fix it. There were two parts to the problem.

First, I had multiple Codex installations, including npm and standalone versions. I removed all of them and installed Codex again from scratch using the official standalone installer.

The main issue, however, was the model cache. My Mac Codex app had an active remote connection to the EC2 instance. Because of that, the Codex app-server and proxy processes on EC2 kept restarting whenever I killed them. They were also restoring the old model cache, so deleting the cache alone didn’t work.

What fixed it:

  1. Remove all npm and standalone Codex installations.
  2. Reinstall Codex using the official standalone installer.
  3. Close the Codex app on the Mac or disconnect its remote connection to EC2.
  4. On EC2, find the running Codex processes:
pgrep -a -u "$USER" -f 'codex|app-server|proxy'
  1. Kill the listed processes and confirm they don’t restart:
kill <PID1> <PID2>
pgrep -a -u "$USER" -f 'codex|app-server|proxy'
  1. Delete the cached model data:
CODEX_DIR="${CODEX_HOME:-$HOME/.codex}"

rm -rf ~/.codex/cache
  1. Start Codex again.

After that, GPT-5.6 appeared in the model list and worked normally. I didn’t need to log in again.