Cairn
NousResearch/hermes-agent

pooled remote probe timeout vs cold-start duration

Cluster 107997. Data as of

Nothing open on GitHub. Fix merged in #108112 on 11 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 #108112. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #108112. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items address a mismatch where the dispatch-probe timeout for pooled remote backends is shorter than the backend cold-start time, causing repeated probe failures and reconnect storms. The work involves adjusting the liveness budget given to pooled remote dispatch probes to accommodate cold-start delays.

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.

  • #108112 Desktop: clicking a pooled remote profile no longer storms reconnects while the VPS backend cold-starts (#107997, salvage #108009 #97914)

    merged to main

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

2 PRs closed without merging

From the close comments: done elsewhere 1 · duplicate 1

  • #108009 fix(desktop): give pooled remote dispatch probes the cold-start liveness budget · done elsewhere → d1bd7b0, #108112, #97914
  • #108016 fix(desktop): reuse liveness timeout for pooled dispatch probe to avoid cold-start storm (#107997) · duplicate → #108009, #107997
Closed issues · 1
  • Closed#107997[Bug]: Pooled remote backend dispatch-probe timeout (2500ms) is shorter than backend cold-start (~6-8s), causing guaranteed probe failure and self-reinforcing reconnect storms
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
#108112
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
11 Sep 2026

For your agent

The same facts, typed.

cluster/107997.json
cluster/107997.md