/model does not list GPT-5.6 models that are available via -m

I also have this bug on fedora cli.

Trying to run any commands results in this error:

■ {"type":"error","status":400,"error":
{"type":"invalid_request_error","message":"The 'gpt-5.6-sol' model
requires a newer version of Codex. Please upgrade to the latest app or
CLI and try again."}}

Blocking ab.chatgpt.com and removing leveldb can be temporary solution, as it relates to filter policies obtained online.

On Windows you can add 127.0.0.1 ab.chatgpt.com to C:\Windows\System32\drivers\etc\hosts and delete ~\AppData\Local\Packages\OpenAI.Codex_<some hash>\LocalCache\Roaming\Codex\web\Codex\Default\Local Storage\leveldb

The comment is sent by an agent, behalf of @Menci.

The ab.chatgpt.com block workaround upthread works but disables every Statsig gate (Browser Use, Computer Use, plugin catalog, etc.). Here's a more targeted patch that only defeats the picker whitelist.

Filter location (Codex/ChatGPT.app 26.707.31428, com.openai.codex):

webview/assets/app-initial~app-main~onboarding-page~...~k0ede4gb-C17KDkOa.js:

• $v(e) — zod-parses use_hidden_models, available_models, default_model off the Statsig dynamic-config payload
• ay() — reads eee('107580212').value
• Jv({authMethod:e, availableModels:t, models:a, useHiddenModels:o}) — the picker filter:

``js
let l = o && e !== 'amazonBedrock';
a.forEach(n => { if (l ? t.has(n.model) : !n.hidden) { /* keep */ } });
``

Verify live (paste into DevTools console once you have one on the app):

Object.values(__STATSIG__.instances)[0].getDynamicConfig('107580212').value
// -> { use_hidden_models: true, default_model: 'gpt-5.4',
//      available_models: ['gpt-5.5','gpt-5.4','gpt-5.4-mini','gpt-5.3-codex','gpt-5.2'] }

For any non-ChatGPT-authed session (API-key, Azure, custom OpenAI-compatible) the whitelist branch runs and every hidden:false model that app-server model/list returned — gpt-5.6-{sol,terra,luna} included — gets stripped, even though the CLI running from the same bundle can invoke them fine.

One-byte shim (per-install; gets wiped by Sparkle):

ASAR=/Applications/ChatGPT.app/Contents/Resources/app.asar
OFF=$(grep -aboE 'use_hidden_models' "$ASAR" | head -1 | cut -d: -f1)
printf 'Z' | dd of="$ASAR" bs=1 seek=$((OFF+16)) count=1 conv=notrunc
codesign --force --deep --sign - /Applications/ChatGPT.app

Renames the string literal inside $v() so safeParse(e.use_hidden_models) misses and the field defaults to false. Length-preserving (asar header untouched), idempotent, reversible. Works because EnableEmbeddedAsarIntegrityValidation fuse is OFF on shipped builds.

Fix at the source — any one of these:

1. In Jv/ive: skip the whitelist branch when authMethod !== 'chatgpt'. Custom API-key providers shouldn't be gated by a ChatGPT-account-scoped rollout list.
2. In Jv/ive: union availableModels with models.filter(m => !m.hidden) before the t.has() check, so provider-returned visible models can never be dropped.
3. Server-side: exclude non-ChatGPT-authed sessions from Statsig config 107580212 targeting.

Happy to help verify a fix if useful.

Possibly a separate cause, but I reproduced the same symptom on Linux with CLI 0.144.1.

~/.codex/models_cache.json showed client_version: 0.141.0 and no GPT-5.6 entries because older Codex/app-server processes were still running and overwriting the shared cache.

After stopping the stale processes and rebuilding the cache:

mv ~/.codex/models_cache.json ~/.codex/models_cache.json.old
codex debug models >/dev/null

it regenerated as 0.144.1 with Sol, Terra, and Luna marked visibility: list, and /model worked.

Affected users may want to compare codex --version with the cache’s client_version and check for old processes using:

ps -eo pid,lstart,args | grep '[c]odex'

This may be because you have a stale (older) app server running locally, and the newly launched TUI is connecting to it. Make sure to terminate any local app server instances, then run the latest version of the CLI.