NousResearch/hermes-agent

Dashboard respawn errors logged incorrectly in receipts

Cluster 109290 · hermes cli. Data as of 2026-10-27 11:58 UTC

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

open issues

open PR

items grouped

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

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

Read #126149 Pick up a Lab task

These issues and PRs concern a bug where a dashboard respawn that ends in errors is misreported as 'restarted' or 'success' in update receipts, because the outcome-matching logic cannot express respawn "failed" states. Work focuses on correcting how failing respawns are recorded and restoring manual dashboards after a PM takeover.

Open issues0

No open issues.

Open PRs1

PR#109300fix(update): stop failed dashboard restores from reading as success

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#126149 fix(update): bring a manual dashboard back after the PM takeover, and book a failed respawn as failed

merged to main

files: hermes_cli/main_dashboard.py, hermes_cli/update_cmd_fleet.py, hermes_cli/update_cmd_maint.py, hermes_cli/update_inventory.py, tests/e2e/core/upgrade/handoff/_handoff.py, tests/e2e/core/upgrade/handoff/_scenario.py, tests/hermes_cli/test_old_updater_takeover.py, tests/hermes_cli/test_restart_plan_reconciliation.py, tests/hermes_cli/test_update_stale_dashboard.py

1 PR closed without merging

From the close comments: other 1

#109298 fix(update): record a failed dashboard respawn as "failed" in the receipt · other → #126149

Closed issues · 1

Closed#109290[Bug]: update receipt records a failed dashboard respawn as "restarted" — match_runtime_outcomes cannot express respawn failure

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.50: 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: #126149
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 28 Sep 2026

For your agent

The same facts, typed.

cluster/109290.json
cluster/109290.md