Cairn

Desktop backend respawn after stale exit failures

NousResearch/hermes-agent · cluster 112344

Data as of

Nothing open on GitHub. Fix merged in #113180. Check it covers your case.

The short answer

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

These issues and fixes address a bug where the desktop app's local backend fails to respawn after being classified as a stale exit, leaving the UI running without an engine. The work focuses on making backend recovery logic more robust and independent of pool state.

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.

  • #113180 fix(desktop): local backend respawns after a stale-classified exit and exit lines carry the backend's last output (#112344, salvage #112349, #112356)

    merged to main

    files: apps/desktop/electron/backend-claim.test.ts, apps/desktop/electron/backend-claim.ts, apps/desktop/electron/backend-exit-recovery.test.ts, apps/desktop/electron/backend-exit-recovery.ts, apps/desktop/electron/main.ts, website/docs/user-guide/desktop.md

3 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1

  • #112345 fix(desktop): recover after backend exit · superseded by another PR → #113180, #112344
  • #112356 fix(desktop): respawn when stale backend exit leaves no owner · done elsewhere → 8e5b0e2, #112344, #113180, #112349, #112356
  • #112989 fix(desktop): keep primary recovery independent from pool state · superseded by another PR
Closed issues · 1
  • Closed#112344[Bug][Desktop/Windows] Desktop app logs "Ignoring stale Hermes backend exit (1)" and never respawns the backend — UI keeps running with no engine (9 h observed)
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.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
#113180
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
17 Sep 2026

For your agent

The same facts, typed.

cluster/112344.json
cluster/112344.md