NousResearch/hermes-agent

Desktop SSH remote boot instability on slow hosts

Cluster 97264. Data as of 2026-10-30 11:57 UTC

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

open issues

open PRs

items grouped

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

Next step: read #128417, then check it covers your case.

Read #128417 Pick up a Lab task

These items concern instability when booting remote SSH backends on slow hosts, specifically around a hardcoded ready timeout and cleanup logic that can tear down the shared ControlMaster, creating a problematic cycle. The group also touches on dropping stale pooled remote backends.

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.

#128417 fix(desktop): drop dead pooled remote backends and tolerate slow remote cold boots

merged to main

files: apps/desktop/electron/main.ts, apps/desktop/electron/remote-lifecycle.test.ts, apps/desktop/electron/remote-lifecycle.ts, apps/desktop/electron/remote-liveness.test.ts, apps/desktop/electron/remote-liveness.ts, apps/desktop/electron/windows-remote-lifecycle.ts

1 PR closed without merging

From the close comments: done elsewhere 1

#97392 fix(desktop): remote SSH boot instability on slow hosts (ready timeout + shared master teardown) · done elsewhere → 8ab0896, #97264, #100040

Closed issues · 1

Closed#97264Desktop SSH boot instability on slow hosts: hardcoded 45s ready timeout + failed-attempt cleanup kills the shared ControlMaster (vicious cycle)

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

Merged PRs: #128417
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 30 Sep 2026

For your agent

The same facts, typed.

cluster/97264.json
cluster/97264.md