Codex session looping on false 401 token_expired
Cluster 88510 · agent. Data as of
Nothing open on GitHub. Fix merged in #115749 on 19 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 #115749. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115749. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where persisted or resumed Codex sessions repeatedly encounter a 401 token_expired error despite the token being valid, while fresh sessions with the same token work correctly. The work involves fixing how lingering token_expired state is handled in the replay cache during session resumption.
Open issues0
Open PRs0
Fixes on record
-
#115749 fix(codex): resumed session no longer loops on 401 token_expired with cached reasoning (#88510, salvage #88541)
files:
agent/turn_recovery.py,tests/agent/test_codex_token_expired_replay_recovery.py,website/docs/developer-guide/provider-runtime.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#88541 fix(codex): recover lingering token_expired after replay cache · merged via another change →
fbbc7df,#115749,#88510,#88541
Closed issues · 1
- Closed#88510[Bug]: Persisted Codex session loops on false 401 token_expired while fresh sessions with the same token work
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
- #115749
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026