Repository navigation
■ Your access token could not be refreshed because your refresh token was revoked. Please log out and sign in again. #1
Description
What version of Codex CLI is running?
codex-cli 0.128.0, 0.125.0 (codext)
What subscription do you have?
Plus
Which model were you using?
GPT 5.5 xhigh
What platform is your computer?
Microsoft Windows NT 10.0.26200.0 x64
What terminal emulator and version are you using (if applicable)?
Windows Terminal
What issue are you seeing?
■ Your access token could not be refreshed because your refresh token was revoked. Please log out and sign in again.
This error crops up when switching back to any other account.
What steps can reproduce the bug?
Switch back to a previous account and send a message.
What is the expected behavior?
Able to send a message.
Additional information
No.
Activity
Loongphy commentedon May 8, 2026
This is normal behavior.
Codex typically refreshes the local auth.json file approximately every 8 days. Let’s call the initial state 'A'.
At some point, your account's auth.json may have been updated to 'B', but failed to sync properly—for instance, if codex-auth was never executed, preventing the update of the local file, which remained as 'A'.
Consequently, when you switched back to the account, the system continued using the outdated auth.json, leading to this issue.
SkiesOfTheKuth commentedon May 18, 2026
No. I added it literally minutes apart. It didn't go stale.
Loongphy commentedon May 21, 2026
Are you using this with codex-auth?
This looks like an issue caused by codex-auth account synchronization. You might want to try updating to the latest version, 0.2.9.