# NousResearch/hermes-agent · Desktop app 90s boot timeout race condition fixes

## Open now

- 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.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #96315: Desktop app: backend readiness race causes reproducible 90s boot timeout

## Prior & competing PRs

- **#96347: fix(desktop): make backend port-announcement wait multi-channel — closes the 90s boot-timeout family (#96315)**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `6d4e851d8`
- **#96468: fix(desktop): arm the backend READY scanner at spawn instead of after the claim (#96315)**. closed without merge
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `#60986`, `#96347`, `#96468`, `#96315`

## Fix status

- No merged fix on record.