NousResearch/hermes-agent

Desktop app 90s boot timeout race condition fixes

Cluster 96315. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A reproducible ~90-second startup timeout in the desktop app caused by race conditions where backend READY signals could be missed before listeners attached. Multiple fixes address the timing and sequencing of backend readiness detection.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · partial fix 1

  • #96347 fix(desktop): make backend port-announcement wait multi-channel — closes the 90s boot-timeout family (#96315) · done elsewhere → 6d4e851
  • #96468 fix(desktop): arm the backend READY scanner at spawn instead of after the claim (#96315) · partial fix → #60986, #96347, #96468, #96315
Closed issues · 1
  • Closed#96315Desktop app: backend readiness race causes reproducible 90s boot timeout
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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.