Cairn

Dashboard chat data loss on WebSocket/session issues

NousResearch/hermes-agent · cluster 53700 · dashboard

Data as of

Nothing open on GitHub. Fix merged in #78313. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 2 issues already closed.
Fix event
A fix was merged to main in PR #78313. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this partially resolved, deciding PR #78313. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and fixes concern dashboard chat losing messages or chunks after WebSocket reconnects or dashboard restarts, related to stale session tokens and loopback tab reloading.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #78313 fix(dashboard): reload loopback tabs after stale session-token closes

    merged to main

    files: apps/shared/src/json-rpc-gateway.ts, web/src/components/ChatSidebar.test.tsx, web/src/components/ChatSidebar.tsx, web/src/components/HermesConsoleModal.tsx, web/src/lib/api.test.ts, web/src/lib/api.ts, web/src/lib/dashboard-auth-reload.test.ts, web/src/lib/dashboard-auth-reload.ts, web/src/lib/gatewayClient.test.ts, web/src/lib/gatewayClient.ts, web/src/pages/ChatPage.test.tsx, web/src/pages/ChatPage.tsx

1 PR closed without merging

From the close comments: merged via another change 1

  • #54022 fix(dashboard): reload loopback tabs after stale session-token closes · merged via another change → #78313
Closed issues · 2
  • Closed#53700[Bug] Dashboard chat loses last message after WebSocket reconnect
  • Closed#53972[Bug] Dashboard chat loses random chunks + token_mismatch spam after dashboard restart
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.56: 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
Merged PRs
#78313
Closed issues
2
Attempts
1 PR closed without merging
Fix link checked
4 Aug 2026

For your agent

The same facts, typed.

cluster/53700.json
cluster/53700.md