Desktop session loss and reconnect after disconnect

NousResearch/hermes-agent · cluster 46563 · apps/desktop

Data as of

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

The short answer

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

These issues and fixes address the desktop (and TUI) losing active sessions or chat history after WebSocket disconnects, sleep/wake cycles, or orphan-reaping logic. Work covers persisting pins, correctly resuming existing sessions on reconnect, and preventing gateway-owned sessions from being incorrectly terminated.

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.

  • #122865 fix(desktop): preserve the active chat across a sleep/wake gateway reconnect

    merged to main

    files: apps/desktop/src/app/session/hooks/use-route-resume.test.tsx, apps/desktop/src/app/session/hooks/use-route-resume.ts

1 PR closed without merging

From the close comments: closed without comment 1

  • #53522 fix(desktop): preserve active chat on reconnect · closed without comment
Closed issues · 3
  • Closed#46563[Bug] Hermes Desktop: Session content disappears after WebSocket disconnect — pinned chat history lost
  • Closed#52089Desktop app loses conversation after sleep/wake — data persists but UI can't find session
  • Closed#53374Desktop GUI creates new session after Windows sleep (WebSocket disconnect, session context lost)
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.27: 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
apps/desktop
Merged PRs
#122865
Closed issues
3
Attempts
1 PR closed without merging
Fix link checked
25 Sep 2026

For your agent

The same facts, typed.