NousResearch/hermes-agent

Hermes update receipt persistence and reliability fixes

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

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

open issues

open PR

items grouped

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

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

Read #113105 Pick up a Lab task

These issues and PRs address scenarios where Hermes update receipts were not written or were lost, including cases involving module-state loss, failed updates, and dashboard cleanup crashes. The work focuses on ensuring receipts are consistently persisted and that write failures are surfaced.

Open issues0

No open issues.

Open PRs1

PR#112549fix(update): retain failed update receipts after state loss

Fixes on record

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

#113105 hermes update always leaves a receipt; a stale-symbol dashboard cleanup crash no longer fails the update (#112604, #112465, #112558)

merged to main

files: hermes_cli/AGENTS.md, hermes_cli/update_cmd_maint.py, hermes_cli/update_receipt.py, tests/hermes_cli/test_update_receipt.py, tests/hermes_cli/test_update_stale_dashboard.py, tests/hermes_cli/test_update_stale_module_purge.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

#112468 fix(update): persist receipts across module-state loss · done elsewhere → 4768534, #113105, #112465
#113159 fix(update): a real update leaves its receipt; receipt write failures are visible (#112465, part of #112558) · superseded by another PR → 1259b14, 5f071fb, 4768534

Closed issues · 1

Closed#112465hermes update writes no receipt on v0.21.3 even with the `hermes_cli.update_` purge protection in place

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: #113105
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 16 Sep 2026

For your agent

The same facts, typed.

cluster/112465.json
cluster/112465.md