Cairn
NousResearch/hermes-agent

Desktop SSH session token persistence fix

Cluster 103795. Data as of

Nothing open on GitHub. Fix merged in #104521 on 6 Sep 2026. Check it covers your case.

The short answer

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

A bug caused desktop SSH remote connections to enter a 403 WebSocket dial loop because persisted registry tokens were rejected after restarts or renames. The fix ensures SSH session tokens are retained correctly in the v2 connection registry.

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.

  • #104521 fix(desktop): SSH connections keep their session token across restarts and renames — no more 403 WS loop (#103795, salvage #103826)

    merged to main

    files: apps/desktop/electron/connection-registry.test.ts, apps/desktop/electron/connection-registry.ts

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #103826 fix(desktop): keep the ssh session token in the v2 connection registry (#103795) · merged via another change → d86627a, #104521, #103795, #103831
  • #103831 fix: [Bug]: Desktop SSH remote Bot Chat stuck in 403 WS dial loop - persisted registry token is rejected by the backend it was persisted for (#103795) · done elsewhere → #103795, #104521
Closed issues · 1
  • Closed#103795[Bug]: Desktop SSH remote Bot Chat stuck in 403 WS dial loop - persisted registry token is rejected by the backend it was persisted for
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.50: 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

Merged PRs
#104521
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
6 Sep 2026

For your agent

The same facts, typed.

cluster/103795.json
cluster/103795.md