›_ Codex Issues
Codex Issues / #25443

Codex Desktop gets stuck with refresh-token-revoked auth error during active session

Open 💬 5 comments Opened May 31, 2026 by GGBondBlueWhale
💡 Likely answer: A maintainer (github-actions[bot], contributor) responded on this thread — see the highlighted reply below.

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?

  1. Open Codex Desktop on macOS.
  2. Work in an active Codex session.
  3. During normal usage, Codex Desktop enters an auth failure state.
  4. The active session/input area shows the refresh-token-revoked error quoted above.
  5. 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.

View original on GitHub ↗

5 Comments

github-actions[bot] contributor · 2 months ago

Potential duplicates detected. Please review them and close your issue if it is a duplicate.

  • #25379
  • #24365

Powered by Codex Action

etraut-openai contributor · 2 months ago

The /feedback code path doesn't require authentication, and it doesn't modify your auth token. I suspect this was a coincidence. Have you seen this more than once? Are you able to repro?

GGBondBlueWhale · 2 months ago
The /feedback code path doesn't require authentication, and it doesn't modify your auth token. I suspect this was a coincidence. Have you seen this more than once? Are you able to repro?

Thanks for the clarification. Yes, I agree this is likely not caused by /feedback.

To clarify, the auth error appeared first during the active Codex Desktop session. I submitted feedback only after seeing the error, so the feedback ID is just for diagnostics.

So far I have only observed this specific “refresh token was revoked” state once in this Codex Desktop session, and I do not yet have a deterministic repro. The visible sequence was:

  1. Codex Desktop was already signed in and working in an active session.
  2. The session suddenly became unable to continue.
  3. The UI showed: “Your access token could not be refreshed because your refresh token was revoked. Please log out and sign in again.”
  4. I then uploaded feedback to report the already-existing auth failure.

I will update the issue if I see it again or find a reliable way to reproduce it.

ITFinesse · 2 months ago

happens in va code

zdimension · 2 months ago

Getting this in VS Code, same behavior.