Hello — I’m looking for help with a reproducible Codex Desktop authentication issue on Windows.
Impact
Codex Desktop launches and completes sign-in, and Settings can be opened normally. However, opening any thread immediately redirects the app to the login page. Remote access to the existing thread continues to work, so the account itself still appears logged in elsewhere.
Environment
Windows 10 Pro 10.0.19045 x64
Codex Desktop MSIX 26.818.5229.0
codex-cli 0.149.0
Sign-in method: Continue with Google
Observed: 2026-08-24, UTC+8
Sanitized error
The Desktop logs repeatedly show /wham/tasks/list failing with:
code: token_revoked
Encountered invalidated oauth token for user, failing request
Non-destructive debugging already completed
Refreshed CLI authentication successfully.
Fully exited Desktop and verified that no ChatGPT/Codex processes remained.
Reversibly renamed the complete Desktop Chromium profile under %APPDATA%\Codex\web\Codex, then allowed Desktop to generate a fresh profile.
Reproduced the same redirect with the fresh profile.
Completed a new interactive OAuth login using Continue with Google; the local authentication file was rewritten.
Reproduced token_revoked immediately afterward.
With Desktop closed, codex login status reports “Logged in using ChatGPT” with exit code 0. This only confirms the CLI recognizes local authentication; it does not prove the CLI exercised /wham/tasks/list.
Nothing was deleted. The original Desktop profile remains preserved as a reversible backup, and project repositories, SSH configuration, and session transcripts were not modified.
Current finding
Because the failure survives both a completely fresh Desktop profile and a new Google OAuth login, the local Chromium/profile cache does not appear to be the sole cause. This may involve a server-side revoked session/account state, or the Windows Desktop build obtaining a token that /wham/tasks/list rejects.
OpenAI Support has already escalated the case to a support specialist, but Desktop remains unusable while I wait.
Questions
Is anyone else reproducing this on Windows build 26.818.5229.0?
Is there a supported device-code login flow for this Desktop build?
Is a server-side OAuth/session reset sometimes required for this condition?
Which sanitized request/correlation identifiers would be most useful to collect?
No OAuth token, refresh token, Cookie database, auth.json contents, SSH key, project file, or full transcript is included. Please do not post authentication secrets when comparing results.
You are welcome to discuss Codex issues here. However, the official place to report and track them is the OpenAI Codex GitHub issue tracker.
I asked ChatGPT to look for the closest related issue, and it identified:
If that issue matches your problem, consider adding a reaction on the GitHub issue itself—not only on this forum topic. Reactions on GitHub can help the developers gauge the number of affected users.
If it does not describe the same problem, search the existing Codex issues for a closer match. If you cannot find one, open a new issue and include as much relevant detail as possible.
I’m seeing a very similar issue on Windows Codex Desktop.
In my case, sign-in succeeds, then Desktop later loses auth state and I also started seeing intermittent conversation creation timeouts and no rollout found for thread id.
Codex CLI works normally on the same Windows machine with the same account.
I also opened a GitHub issue in the OpenAI Codex repository: issue #40704.
This may be part of the same broader Desktop auth/session regression.
reaction on the GitHub issue itself—not only on this forum topic. Reactions on GitHub can help the developers gauge the number of affected users.