What version of the Codex App are you using?
Not provided. The issue is reproducible in the Codex app when the last selected workspace is expired or deactivated.
What subscription do you have?
Not provided.
What platform is your computer?
Not provided.
What issue are you seeing?
The Codex app becomes unusable when the currently selected workspace is expired or deactivated.
A very similar issue previously happened in ChatGPT: when trying to log in while the selected workspace was expired/deactivated, ChatGPT would show a "workspace deactivated" state and the user could not proceed unless they deleted cookies/site data from the browser. That appears to have been fixed in ChatGPT: it now lets the user switch to or join their personal workspace instead of getting stuck.
Codex still appears to have the old failure mode. When the selected workspace is expired/deactivated, Codex opens to a blank screen and does not provide a way to log out, switch workspace, or recover from inside the UI.
Related issue: #20125 reports a blank/white Codex Desktop window for stale/invalidated auth tokens. This report appears related, but the trigger here is an expired/deactivated workspace rather than only an invalidated token.
What steps can reproduce the bug?
- Have a ChatGPT/Codex account where a workspace has expired or been deactivated.
- Ensure Codex is currently associated with, or last selected, that expired/deactivated workspace.
- Open the Codex app.
- Observe that the app renders a blank screen and offers no UI recovery path.
What is the expected behavior?
Codex should handle expired/deactivated workspaces the same way ChatGPT now appears to handle them:
- Show a useful workspace expired/deactivated message.
- Allow switching to a personal workspace.
- Allow logging out from the UI.
- Avoid rendering a blank/unusable screen.
- Avoid requiring manual local file edits to recover.
What is the actual behavior?
Codex shows a blank screen and becomes unusable. There is no visible way to log out, switch workspace, or recover from inside the app.
Workaround
The only workaround found is to manually go into the local Codex files and log out from there. After doing that and reopening Codex, the app becomes usable again.
Why this matters
Users can get locked out of Codex entirely if their last selected workspace expires or is deactivated. This is especially confusing because ChatGPT now appears to handle the same workspace state correctly by letting the user continue with their personal workspace.
Suggested fix
Codex should detect the expired/deactivated workspace/auth state and render a recovery screen with at least:
- Switch to personal workspace
- Log out / sign in again
- Clear stale workspace selection
This would prevent the blank-screen failure and avoid requiring users to manually edit local Codex files.
What version of the Codex App are you using?
Not provided. The issue is reproducible in the Codex app when the last selected workspace is expired or deactivated.
What subscription do you have?
Not provided.
What platform is your computer?
Not provided.
What issue are you seeing?
The Codex app becomes unusable when the currently selected workspace is expired or deactivated.
A very similar issue previously happened in ChatGPT: when trying to log in while the selected workspace was expired/deactivated, ChatGPT would show a "workspace deactivated" state and the user could not proceed unless they deleted cookies/site data from the browser. That appears to have been fixed in ChatGPT: it now lets the user switch to or join their personal workspace instead of getting stuck.
Codex still appears to have the old failure mode. When the selected workspace is expired/deactivated, Codex opens to a blank screen and does not provide a way to log out, switch workspace, or recover from inside the UI.
Related issue: #20125 reports a blank/white Codex Desktop window for stale/invalidated auth tokens. This report appears related, but the trigger here is an expired/deactivated workspace rather than only an invalidated token.
What steps can reproduce the bug?
What is the expected behavior?
Codex should handle expired/deactivated workspaces the same way ChatGPT now appears to handle them:
What is the actual behavior?
Codex shows a blank screen and becomes unusable. There is no visible way to log out, switch workspace, or recover from inside the app.
Workaround
The only workaround found is to manually go into the local Codex files and log out from there. After doing that and reopening Codex, the app becomes usable again.
Why this matters
Users can get locked out of Codex entirely if their last selected workspace expires or is deactivated. This is especially confusing because ChatGPT now appears to handle the same workspace state correctly by letting the user continue with their personal workspace.
Suggested fix
Codex should detect the expired/deactivated workspace/auth state and render a recovery screen with at least:
This would prevent the blank-screen failure and avoid requiring users to manually edit local Codex files.