Cairn
NousResearch/hermes-agent

Desktop-supervised serve restart during fleet updates

Cluster 111494. Data as of

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

The short answer

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

These items concern a bug where the desktop restart mechanism cannot restart a desktop-supervised serve process during reconciliation, causing update failures and repeated fleet_restart_pending states. The cluster includes a bug report and related fix attempts addressing this handoff problem.

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.

  • #112312 fix(update): Desktop-owned serve no longer fails hermes update or holds fleet_restart_pending (#111494, supersedes #111499)

    merged to main

    files: hermes_cli/update_abort_recovery.py, hermes_cli/update_cmd_fleet.py, hermes_cli/update_inventory.py, tests/hermes_cli/test_update_fleet_restart_pending.py, tests/hermes_cli/test_update_serve_generation_recovery.py

1 PR closed without merging

From the close comments: merged via another change 1

  • #111499 fix(update): discharge Desktop serve restart handoff · merged via another change → 7c6b8c7, #112312
Closed issues · 1
  • Closed#111494[Bug]: the `desktop` restart mechanism is undischargeable — the restart phase is forbidden to restart a desktop-supervised `serve` while reconciliation demands it, so every Desktop-present update exits 1 and re-arms `fleet_restart_pending`
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
#112312
Closed issues
1
Attempts
1 PR closed without merging
Fix link checked
16 Sep 2026

For your agent

The same facts, typed.

cluster/111494.json
cluster/111494.md