NousResearch/hermes-agent

Fleet-restart marker discharge edge cases

Cluster 115638 · hermes cli. Data as of

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

The short answer

0open issues
1open PR
5items grouped
Known?
Yes. 5 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
0 issues and 1 PR.

These issues and pull requests address scenarios where fleet_restart_pending markers become stuck or undischargeable, particularly when updates crash mid-cleanup, when no inventory or plan runtimes are recorded, or when no obligation exists but the fleet is already current.

Open issues0

No open issues.

Open PRs1

  • PR#115663fix(update): re-probe the fleet when arming a marker with no plan runtimes

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

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #115652 fix(update): discharge inventory-less fleet-restart markers on live-fleet evidence · merged via another change → 5d17001, #116710, #115638, #115311, #115090, #115652, #115330
  • #116090 fix(cli): discharge fleet_restart_pending marker on aborted cleanup (#115638) · superseded by another PR → #116710
Closed issues · 1
  • Closed#115638fleet_restart_pending marker is undischargeable when `hermes update` crashes mid-cleanup
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

Subsystem
hermes cli
Merged PRs
#116710
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.