Cairn

Fix: stop_reason misread as unfinished update receipt

NousResearch/hermes-agent · cluster 103590

Data as of

Nothing open on GitHub. Fix merged in #104153. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #104153. 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
Nothing open on GitHub.

A bug where a successful update's stop_reason field caused _receipt_looks_unfinished() to incorrectly flag the update as incomplete, triggering persistent warnings and repeated fleet restarts. These issues and fixes address correcting that misclassification.

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.

  • #104153 fix(update): a successful update no longer re-arms the fleet restart forever (#98022, salvage #97547)

    merged to main

    files: hermes_cli/main.py, hermes_cli/update_cmd_fleet.py, hermes_cli/update_receipt.py, tests/hermes_cli/test_update_fleet_restart_pending.py, tests/hermes_cli/test_update_handoff_exit.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · duplicate 1

  • #103613 fix(cli): success update receipt with stop_reason is not unfinished (#103590) · done elsewhere → cd27df3, #104153, #97547
  • #103618 fix(update): do not treat successful stop_reason as unfinished receipt (#103590) · done elsewhere → cd27df3, #104153, #97547
  • #103691 fix(update): do not classify successful update receipt as unfinished when stop_reason is recorded · duplicate → #97547, #103590, #103613, #103618
Closed issues · 1
  • Closed#103590[Bug]: successful update writes stop_reason, so _receipt_looks_unfinished() misreads it as unfinished — 'pre-update modules' warning never clears
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

Merged PRs
#104153
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
6 Sep 2026

For your agent

The same facts, typed.

cluster/103590.json
cluster/103590.md