Codex usage endpoint 401 token refresh handling
Cluster 111007 · agent. Data as of
1 open item. Fix merged in #111476 on 15 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111476. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111476. That is separate from the fix event. - Still open
- 0 issues and 1 PR.
A bug report and related fix attempts addressing how the Codex /usage path handles server-revoked access tokens, specifically adding a forced refresh on 401 rather than relying solely on local JWT expiry.
Open issues0
Open PRs1
- PR#111022fix(auth): restore Codex usage after revoked-token 401
Fixes on record
-
#111476 fix(codex): /usage recovers from a server-revoked token with a forced refresh on 401 (#111007, salvage #111022)
files:
agent/account_usage.py,hermes_cli/auth_codex.py,tests/agent/test_account_usage.py,tests/hermes_cli/test_auth_codex_provider.py
Closed issues · 1
- Closed#111007[Bug]: Codex /usage never recovers from a server-revoked access token — refresh trusts local JWT exp only, no 401-triggered retry on the quota path
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #111476
- Closed issues
- 1
- Attempts
- 0 PRs closed without merging
- Fix link checked
- 15 Sep 2026