What version of the Codex/ChatGPT App are you using?
26.715.12143
What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows x64 (work-managed PC; exact Windows build not currently available)
What issue are you seeing?
In the unified ChatGPT desktop app, Chat mode correctly shows GPT-5.6, but Work mode only shows an older model catalog (GPT-5.5, GPT-5.4, and GPT-5.4 Mini).
This happens only on one Windows PC at work. With the same ChatGPT account:
- Work mode shows GPT-5.6 in the web app.
- Work mode shows GPT-5.6 in the Android app.
- Work mode shows GPT-5.6 on other PCs.
- Chat mode on the affected PC also shows GPT-5.6 correctly.
Therefore, the account is entitled to the model and the problem appears to be a device-local stale model catalog, runtime, cache, or configuration issue specific to Work/Codex.
Steps to reproduce
- Open ChatGPT desktop app version
26.715.12143 on the affected Windows PC.
- Open Chat mode and inspect the model selector.
- Observe that GPT-5.6 is available.
- Switch to Work mode.
- Open a new Work task and inspect the model selector.
- Observe that GPT-5.6 is missing and the newest visible model is GPT-5.5.
Expected behavior
Work mode should load the same current model availability associated with the account and show GPT-5.6, as it does on the web, Android, and other PCs.
Actual behavior
Work mode on this single PC consistently loads an older model list, while Chat mode in the same app loads the current list.
Troubleshooting already attempted
- Fully closed and reopened the app.
- Ended the app process and restarted it.
- Used Windows Repair/Reset for the app.
- Reset did not clear the login/session; the app reopened already authenticated.
- Confirmed that the installed app version is
26.715.12143.
- Confirmed that the issue is not account-wide by testing the same account on web, Android, and other PCs.
- Created new Work tasks; the stale model list remains.
Potentially relevant prior local issue
This same PC previously had a Codex/Work environment problem involving persistent local state and a possibly stale runtime/configuration. The app had reintroduced a Windows sandbox setting ([windows] sandbox = "elevated") and showed an isolated-environment setup warning. There was suspicion at the time of a stale or missing codex.exe runtime path or persistent state under local Codex directories.
That earlier issue may be unrelated, but it suggests that this PC may retain stale Codex runtime/configuration data even after the Windows app reset.
Additional information
The problem looks similar to a renderer/runtime or catalog mismatch rather than a normal staged rollout, because the same account already has GPT-5.6 in Work everywhere except this one device. A supported way to force-refresh the Work model catalog or completely rebuild the local Codex runtime/state would be helpful.
Screenshots are available showing the different model selectors in Chat and Work on the same PC.
What version of the Codex/ChatGPT App are you using?
26.715.12143What subscription do you have?
ChatGPT Plus
What platform is your computer?
Microsoft Windows x64 (work-managed PC; exact Windows build not currently available)
What issue are you seeing?
In the unified ChatGPT desktop app, Chat mode correctly shows GPT-5.6, but Work mode only shows an older model catalog (GPT-5.5, GPT-5.4, and GPT-5.4 Mini).
This happens only on one Windows PC at work. With the same ChatGPT account:
Therefore, the account is entitled to the model and the problem appears to be a device-local stale model catalog, runtime, cache, or configuration issue specific to Work/Codex.
Steps to reproduce
26.715.12143on the affected Windows PC.Expected behavior
Work mode should load the same current model availability associated with the account and show GPT-5.6, as it does on the web, Android, and other PCs.
Actual behavior
Work mode on this single PC consistently loads an older model list, while Chat mode in the same app loads the current list.
Troubleshooting already attempted
26.715.12143.Potentially relevant prior local issue
This same PC previously had a Codex/Work environment problem involving persistent local state and a possibly stale runtime/configuration. The app had reintroduced a Windows sandbox setting (
[windows] sandbox = "elevated") and showed an isolated-environment setup warning. There was suspicion at the time of a stale or missingcodex.exeruntime path or persistent state under local Codex directories.That earlier issue may be unrelated, but it suggests that this PC may retain stale Codex runtime/configuration data even after the Windows app reset.
Additional information
The problem looks similar to a renderer/runtime or catalog mismatch rather than a normal staged rollout, because the same account already has GPT-5.6 in Work everywhere except this one device. A supported way to force-refresh the Work model catalog or completely rebuild the local Codex runtime/state would be helpful.
Screenshots are available showing the different model selectors in Chat and Work on the same PC.