Cairn
NousResearch/hermes-agent

Dashboard PTY WebSocket handshake and streaming fixes

Cluster 19914 · dashboard. Data as of

1 open item. Fix attempted, not merged.

The short answer

0open issues
1open PR
8items grouped
Known?
Yes. 8 related items grouped here, 3 issues already closed.
Fix event
No fix has been merged to main. 4 PRs 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.

Multiple bugs and fixes related to the dashboard's /api/pty WebSocket endpoint, covering handshake timeouts, empty responses, event loop blocking, and loopback connectivity for the PTY sidecar. The work spans FastAPI compatibility, in-container networking, and async offloading of PTY operations.

Open issues0

No open issues.

Open PRs1

  • PR#19938fix(tui): accept WebSocket handshake before close to fix FastAPI 0.136 hang on /api/pty

4 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1 · stale or abandoned 1

  • #19943 fix(cli): run dashboard PTY spawn off the event loop · superseded by another PR → #19938
  • #21980 fix(dashboard): connect PTY sidecar via loopback · superseded by another PR → #21988
  • #21988 fix(dashboard): connect PTY sidecar via loopback · stale or abandoned
  • #22873 fix(dashboard): yield event loop after WebSocket accept in pty_ws handler · done elsewhere → d06104a
Closed issues · 3
  • Closed#19914Dashboard TUI WebSocket handshake hangs on FastAPI 0.136 — /api/pty times out
  • Closed#21948Dashboard Chat stuck: /api/pty websocket handshake/connects but never streams frames
  • Closed#22864Dashboard /chat PTY WebSocket can time out before HTTP 101 response flushes
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.20: 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
3
Attempts
4 PRs closed without merging

For your agent

The same facts, typed.

cluster/19914.json
cluster/19914.md