Login/logout flow can end on generic “Oops, an error has occurred” page
Description
Codex can fail during the sign-in/sign-out flow and end up on a generic error page instead of completing authentication.
The UI shows:
Oops, an error has occurred Try again
This appears after using the Codex login/logout flow. Once it happens, the user cannot continue normally from that screen.
Steps to reproduce
- Sign in to Codex.
- Sign out.
- Attempt to sign in again / switch account through the normal authentication flow.
- Codex displays the generic error page shown above.
Expected behavior
Signing out should fully clear the previous authentication state, and the next sign-in should start a clean authentication flow and complete normally.
Actual behavior
The authentication flow can fail and leave Codex on a generic error screen with only a Try again button.
Environment
- Platform: Windows desktop
- Product: Codex
- Area: authentication / login / logout
Additional context
This looks like stale or inconsistent authentication/session state after logout. A screenshot of the error screen is available and shows only the generic message above, without a more specific error code.
It would also help if the error page exposed a diagnostic/error ID so users can include it in bug reports.
3 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I can confirm I'm experiencing exactly the same issue.
Environment:
Symptoms:
Things I've already tried:
None of these resolved the issue.
Relevant log messages include:
This appears to be specific to the Desktop app because Browser and CLI authentication continue to work normally.
The issue started today. Before today, the Desktop app worked normally.
Confirming the same on Windows 10 (ChatGPT Plus). After logging out and switching to a different account through the normal auth flow, the app lands on the generic "Oops, an error has occurred / Try again" screen and does not recover from it. Clicking "Try again" re-renders the same error, and the app remains unusable until a full application restart, after which login proceeds normally. This has persisted across the version I was using before the latest update and is still present after updating, so it is not specific to one release.
This looks closely related to the account-transition/RPC issue described in #39677 (Windows desktop, OAuth account change, "Try again" only reloads the renderer and doesn't rebuild the connection). Happy to provide app logs if useful. Platform: Windows 10.