Usage still being cached when switching accounts in Codex App
Resolved 💬 6 comments Opened Mar 15, 2026 by vinhnx Closed Mar 15, 2026
💡 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)?
Version 26.311.21342 (993)
What subscription do you have?
Plus
What platform is your computer?
Darwin 25.3.0 arm64 arm
What issue are you seeing?
After hitting usage limits on account A, I switched to account B (which has remaining quota), completed OAuth, and resumed the current session — but the app still reports the usage limit from account A. The session appears to be carrying over the previous account's limit state instead of reflecting the newly authenticated account.
What steps can reproduce the bug?
Uploaded thread: 019cef73-03ae-7013-b3f5-7aff21af3818
What is the expected behavior?
The account's plan usage should be refreshed.
Additional information
_No response_
6 Comments
Potential duplicates detected. Please review them and close your issue if it is a duplicate.
Powered by Codex Action
I don't think this is duplicated; this is a separate caching issue.
The remaining usage for the new account won't be reported until after the first prompt is submitted. It is reported in the HTTP header for the response.
@etraut-openai Got it. Thank you for your clarification, I will close this issue for now.
I have this exact same issue in codex for vsc. Sending a new prompt doesn't solve the problem.
Seems like a missing useEffect dependency on the account state? lol