Cairn
NousResearch/hermes-agent

Dashboard connection and launch failure handling

Cluster 71349 · dashboard. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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
1 issue and 1 PR.

These items address dashboard issues around WebSocket reconnection state after model switching, reusing built TUI components, and surfacing PTY close reasons in failure overlays. The common thread is improving how the dashboard handles and communicates connection or launch failures to the user.

Open issues1

  • Issue#71349[Bug]: Dashboard chat stuck in "reconnecting" state after model switch — WebSocket handshake succeeds but UI never becomes usable

Open PRs1

  • PR#133990fix(dashboard): surface the PTY 1011 close reason in the start-failed overlay

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #71625 fix(dashboard): reuse built TUI and report launch failures · superseded by another PR
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
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/71349.json
cluster/71349.md