Cairn
NousResearch/hermes-agent

WS origin guard rejects loopback origins on non-loopback binds

Cluster 131271 · dashboard. Data as of

1 open item. Fix attempted, not merged.

The short answer

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

A WebSocket origin guard incorrectly rejects loopback origins when the server is bound to a non-loopback address, affecting both the gateway and dashboard. Fixes address accepting the Desktop renderer's loopback origin in these configurations.

Open issues0

No open issues.

Open PRs1

  • PR#131498fix(dashboard): accept the packaged Desktop's loopback Origin on a non-loopback bind

1 PR closed without merging

From the close comments: other 1

  • #131277 fix(gateway): accept a loopback ws origin on a non-loopback bind · other → ce83f39
Closed issues · 1
  • Closed#131271Desktop remote connection to a gated serve fails: WS Origin guard rejects the loopback renderer origin
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
dashboard
Closed issues
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/131271.json
cluster/131271.md