Bracketed IPv6 in NO_PROXY breaks OAuth auth path
Cluster 118159. Data as of
Nothing open on GitHub. Fix merged in #131802 on 5 Oct 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131802. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131802. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where bracketed IPv6 addresses (e.g., [::1]) in the NO_PROXY environment variable cause an 'Invalid port' error on the Codex OAuth and token refresh path. The members cover the bug report and related fixes addressing this parsing issue.
Open issues0
Open PRs0
Fixes on record
-
#131802 fix(net): sanitize bracketed-IPv6 NO_PROXY entries so bare httpx clients construct [risk 0.25]
files:
hermes_cli/auth_codex.py,hermes_cli/doctor_connectivity.py,hermes_cli/doctor_live.py,tests/hermes_cli/test_auth_codex_no_proxy_ipv6.py,tests/hermes_cli/test_doctor_live.py,tests/hermes_cli/test_doctor_no_proxy_ipv6.py,tests/test_utils_no_proxy_sanitize.py,utils.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#118159NO_PROXY containing a bracketed IPv6 ([::1]) breaks the Codex OAuth/refresh path with Invalid port: ':1]' while chat keeps working
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.50: 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
- #131802
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 5 Oct 2026