What version of the Codex App are you using (From “About Codex” dialog)?
26.527.31326 (3390)
What platform is your computer?
macOS Tahoe 26.5, MacBook Pro 16-inch, Apple M5 Max, 128 GB RAM
What issue are you seeing?
Codex Desktop can suddenly enter a broken authentication state during an active session. The active chat becomes unusable and the UI shows:
Your access token could not be refreshed because your refresh token was revoked. Please log out and sign in again.
Important clarification: this was not caused by uploading feedback. The feedback was submitted only after this authentication problem had already appeared, in order to report the bug.
Feedback ID for diagnostics only:
019e7d7b-7b3e-7e70-a2b1-e94560dc55a0
This is disruptive because the app loses the ability to continue the current Codex session or submit follow-up changes until the user signs out and signs back in. The current conversation/session context and pending work may be interrupted.
What steps can reproduce the bug?
- Open Codex Desktop on macOS.
- Work in an active Codex session.
- During normal usage, Codex Desktop enters an auth failure state.
- The active session/input area shows the refresh-token-revoked error quoted above.
- Only after seeing this problem, submit feedback from the feedback dialog to report it.
What is the expected behavior?
Codex Desktop should not suddenly get stuck with a revoked refresh-token state during an active session. If re-authentication is genuinely required, the app should provide an in-app recovery flow that preserves the current conversation/session context and pending work, instead of leaving the session unusable.
Additional information
No screenshots are attached. The feedback ID above is provided only as a diagnostic reference for the already-existing auth failure.
What version of the Codex App are you using (From “About Codex” dialog)?
26.527.31326 (3390)
What platform is your computer?
macOS Tahoe 26.5, MacBook Pro 16-inch, Apple M5 Max, 128 GB RAM
What issue are you seeing?
Codex Desktop can suddenly enter a broken authentication state during an active session. The active chat becomes unusable and the UI shows:
Important clarification: this was not caused by uploading feedback. The feedback was submitted only after this authentication problem had already appeared, in order to report the bug.
Feedback ID for diagnostics only:
This is disruptive because the app loses the ability to continue the current Codex session or submit follow-up changes until the user signs out and signs back in. The current conversation/session context and pending work may be interrupted.
What steps can reproduce the bug?
What is the expected behavior?
Codex Desktop should not suddenly get stuck with a revoked refresh-token state during an active session. If re-authentication is genuinely required, the app should provide an in-app recovery flow that preserves the current conversation/session context and pending work, instead of leaving the session unusable.
Additional information
No screenshots are attached. The feedback ID above is provided only as a diagnostic reference for the already-existing auth failure.