# NousResearch/hermes-agent · QQBot WebSocket proxy bypass NO_PROXY fix

## Open now

- 1 issue, 0 PRs open on GitHub.
- #106790: qqbot adapter: WebSocket uses explicit proxy, ignoring NO_PROXY (platform host in NO_PROXY still routed via proxy)

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.

## TL;DR

- 3 member(s): 1 open issue(s), 0 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Open related issues

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

## Prior & competing PRs

- **#106794: fix(qqbot): honor NO_PROXY when opening gateway WebSocket**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#41185`
- **#107153: fix(qqbot): honor NO_PROXY when opening gateway WebSocket**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#41185`, `#48820`, `#106794`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`