NousResearch/hermes-agent

Self-update compatibility and restart marker fixes

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

These items address a TypeError during mixed pre/post-pull module states mid-update and a related issue where fleet-restart markers with no recorded obligation were not settling correctly. The work involves tolerating older function signatures and fixing restart marker resolution logic.

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: superseded by another PR 1

#115521 fix(update): tolerate older main_dashboard signature in update sweep · superseded by another PR → 94ced1a, #117305, #118154

Closed issues · 1

Closed#115466[Bug]: self-update v0.21.1 → v0.21.3 aborts the fleet tail with `TypeError: _find_stale_dashboard_pids() got an unexpected keyword argument 'scope_home'` (mixed pre/post-pull modules) — update lands but is reported failed

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/115466.json
cluster/115466.md