NousResearch/hermes-agent

Fleet-restart obligation stuck on empty inventory bug

Cluster 115311. Data as of 2026-10-26 12:29 UTC

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

open issues

open PRs

items grouped

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

Next step: read #116710, then check it covers your case.

Read #116710 Pick up a Lab task

A bug where an empty or unrecorded fleet-restart obligation could never be discharged, causing the update process to exit with a spurious 'Fleet restart incomplete' error. The members cover the issue report and related fixes addressing this stuck-marker condition.

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.

#116710 fix(update): a fleet-restart marker with no recorded obligation settles once the fleet is current (#115638, #115311, #115090, salvage #115652 #115330)

merged to main

files: hermes_cli/update_cmd_fleet.py, tests/hermes_cli/test_manual_serve_deferral.py, tests/hermes_cli/test_update_fleet_restart_pending.py, tests/hermes_cli/test_update_obligation_identity.py, tests/hermes_cli/test_update_scoped_reconciliation.py, website/docs/getting-started/updating.md

1 PR closed without merging

From the close comments: merged via another change 1

#115330 fix(update): clear the fleet-restart obligation on empty gateway inventories · merged via another change → 5d17001, #116710, #115638, #115311, #115090, #115652, #115330

Closed issues · 1

Closed#115311hermes update exits 1 with "Fleet restart incomplete" after a successful code update — empty fleet_restart_pending obligation can never be discharged

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: #116710
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 20 Sep 2026

For your agent

The same facts, typed.

cluster/115311.json
cluster/115311.md