Nothing open on GitHub. Fix merged in #115626 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 #115626. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115626. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where a second Codex account could be overwritten by a stale singleton refresh replaying old credentials, even after a rotated manual:device_code pool entry. The fixes prevent stale singleton adoption in this scenario.
Open issues0
Open PRs0
Fixes on record
-
#115626 fix(auth): a second Codex account no longer gets overwritten by the first (#106705, salvage #100423 #106788)
files:
agent/credential_pool.py,contributors/emails/[redacted:email],tests/agent/test_credential_pool_codex_singleton_isolation.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#106788 fix(agent): refuse stale singleton adoption over rotated manual:device_code entries (#106705) · merged via another change →
03fee43,#115626,#100423,#106705
Closed issues · 1
- Closed#106705Codex-Pool-Recovery spielt alten Singleton-Refresh erneut ab trotz zentral erneuertem manual:device_code-Pool
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
- Merged PRs
- #115626
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026