Cairn
NousResearch/hermes-agent

Bypass system proxy for loopback CDP connections

Cluster 110565 · agent. Data as of

1 open item. Fix merged in #111405 on 15 Sep 2026. Check it covers your case.

The short answer

0open issues
1open PR
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #111405. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #111405. That is separate from the fix event.
Still open
0 issues and 1 PR.

A bug where websockets>=14 routes loopback CDP connections through the system proxy, breaking browser_exec on macOS. Multiple fix attempts address bypassing the proxy for loopback hosts in browser environments.

Open issues0

No open issues.

Open PRs1

  • PR#110572fix(browser): bypass proxies for loopback hosts in browser child envs

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #111405 fix(browser): loopback CDP dials bypass the macOS system proxy, browser_exec works again (#110565, salvage #110572)

    merged to main

    files: agent/proxy_bypass.py, hermes_cli/browser_connect.py, tests/hermes_cli/test_cli_browser_connect.py, tests/tools/test_browser_env_loopback_no_proxy.py, tests/tui_gateway/test_tui_gateway_server.py, tools/browser_cdp_tool.py, tools/browser_supervisor.py, tools/browser_tool.py, tools/browser_tool_cdp.py, tools/browser_tool_real_profile.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #110570 fix(browser): bypass proxy for loopback CDP · superseded by another PR → #111405
  • #110586 fix(browser): keep loopback CDP dials off system proxies (#110565) · done elsewhere → #111405, #110565
Closed issues · 1
  • Closed#110565[Bug]: browser_exec fails on macOS with a system proxy — websockets>=14 auto-proxies the loopback CDP connection ("CDP WS handshake failed")
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means 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 Lab

At a glance

Subsystem
agent
Merged PRs
#111405
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.

cluster/110565.json
cluster/110565.md