SSH sibling backend retirement during idle-exit fixes
NousResearch/hermes-agent · cluster 106935
Data as of
Nothing open on GitHub. Fix merged in #110025. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #110025. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #110025. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where idle-exit in SSH-isolated Desktop backends incorrectly retires sibling backends still owned by the app, causing live sessions to be disrupted and restarted. Multiple fix attempts approach the problem via keepalive connections, pool recovery preservation, and sibling backend protection.
Open issues0
Open PRs0
Fixes on record
-
#110025 fix(desktop): SSH-isolated backends Desktop owns are no longer retired by idle-exit (#106935, salvage #106959)
files:
apps/desktop/electron/main.ts,apps/desktop/electron/pool-stop.test.ts,apps/desktop/electron/pool-stop.ts,apps/desktop/electron/ssh-bootstrap-coordinator.test.ts,apps/desktop/electron/ssh-bootstrap-coordinator.ts,apps/desktop/electron/ssh-isolated-keepalive.test.ts,apps/desktop/electron/ssh-isolated-keepalive.ts
3 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1 · other 1
-
#106959 fix(desktop): hold SSH-isolated keepalive WS so idle-exit won't retire owned siblings · merged via another change →
39ef1c1,#110025,#106935 -
#106969 fix(desktop): preserve sibling SSH backends during pool recovery · other →
#106959,#106935 -
#107042 fix(desktop): preserve active SSH sibling backends · done elsewhere →
39ef1c1,#106935,#110025,#106959
Closed issues · 1
- Closed#106935Desktop over SSH: the isolated backend's idle-exit (#101626) retires a sibling backend the app still owns, and the app answers by restarting everything, killing live turns
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.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Merged PRs
- #110025
- Closed issues
- 1
- Attempts
- 3 PRs closed without merging
- Fix link checked
- 14 Sep 2026