Prevent status/doctor from persisting Codex credentials
Cluster 68004 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #115730 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 #115730. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115730. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a specific concern that the status and doctor commands should not import, refresh, or persist Codex credentials as a side effect. The work involves making those commands' Codex credential reads strictly read-only.
Open issues0
Open PRs0
Fixes on record
-
#115730 fix(auth): status and doctor never adopt, refresh or persist a Codex login (#68004, salvage #68224)
files:
hermes_cli/auth.py,hermes_cli/auth_codex.py,hermes_cli/models.py,tests/hermes_cli/test_oauth_status_pool_observation.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#68224 fix(auth): make status/doctor Codex reads side-effect-free (read_only) (#68004) · merged via another change →
29bc634,#115730,#68004,#68224
Closed issues · 1
- Closed#68004status and doctor should never import, refresh, or persist Codex credentials
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
- hermes cli
- Merged PRs
- #115730
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026