codex - 💡(How to fix) Fix Codex app blank screen when expired/deactivated workspace is selected [2 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20168Fetched 2026-04-30 06:32:48
View on GitHub
Comments
2
Participants
2
Timeline
6
Reactions
0
Author
Timeline (top)
labeled ×3commented ×2closed ×1

Root Cause

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.

Fix Action

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.

RAW_BUFFERClick to expand / collapse

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?

  1. Have a ChatGPT/Codex account where a workspace has expired or been deactivated.
  2. Ensure Codex is currently associated with, or last selected, that expired/deactivated workspace.
  3. Open the Codex app.
  4. 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.

extent analysis

TL;DR

The most likely fix is to modify Codex to detect expired/deactivated workspaces and render a recovery screen with options to switch to a personal workspace, log out, or clear stale workspace selection.

Guidance

  • Verify that the issue is indeed caused by an expired or deactivated workspace by checking the workspace status before opening Codex.
  • Check if the issue is related to the one reported in #20125, which involves stale/invalidated auth tokens, and see if the solutions discussed there can be applied.
  • Consider implementing a recovery screen in Codex that handles expired/deactivated workspaces, similar to the one in ChatGPT, to provide a better user experience.
  • Test the workaround of manually logging out from local Codex files to confirm that it resolves the issue temporarily.

Example

No code snippet is provided as the issue does not include specific code details.

Notes

The fix may require changes to the Codex app's authentication and workspace management logic. The relationship between this issue and #20125 should be further investigated to ensure that the solution does not introduce new problems.

Recommendation

Apply a workaround by modifying Codex to detect and handle expired/deactivated workspaces, as this will prevent users from getting locked out of the app.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING