Cairn
NousResearch/hermes-agent

QQBot WebSocket proxy bypass NO_PROXY fix

Cluster 106790 · gateway. Data as of

1 open item. Fix attempted, not merged.

The short answer

1open issue
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 0 PRs.

These members address a bug in the QQBot adapter where the gateway WebSocket connection does not respect the NO_PROXY environment variable, causing traffic to be routed through a proxy even when the platform host is listed in NO_PROXY.

Open issues1

  • Issue#106790qqbot adapter: WebSocket uses explicit proxy, ignoring NO_PROXY (platform host in NO_PROXY still routed via proxy)

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: duplicate 1 · superseded by another PR 1

  • #106794 fix(qqbot): honor NO_PROXY when opening gateway WebSocket · duplicate → #41185
  • #107153 fix(qqbot): honor NO_PROXY when opening gateway WebSocket · superseded by another PR → #41185, #48820, #106794
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.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
gateway
Closed issues
0
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/106790.json
cluster/106790.md