NousResearch/hermes-agent

hermes update leaves stale serve runtimes running old code

Cluster 100479. Data as of 2026-10-24 04:06 UTC

Nothing open on GitHub. Fix merged in #100928 on 2 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

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

Read #100928 Pick up a Lab task

A successful hermes update incorrectly credits or ignores unmanaged serve runtimes still running pre-update code, causing cron job ImportErrors. The associated fixes address how the update command handles, warns about, and restarts these surviving runtimes.

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.

#100928 fix(update): a successful update no longer credits or ignores surviving unmanaged serve runtimes (#100479, salvage #100490 + #100493)

merged to main

files: contributors/emails/[redacted:email], hermes_cli/update_cmd.py, hermes_cli/update_inventory.py, tests/hermes_cli/test_restart_plan_reconciliation.py, tests/hermes_cli/test_update_fleet_restart_pending.py

2 PRs closed without merging

From the close comments: merged via another change 2

#100490 fix(update): stop crediting unmanaged serve runtimes with a gateway's restart · merged via another change → 2b7132c, #100928
#100493 fix(update): warn surviving pre-update serve and dashboard runtimes on success (#100479) · merged via another change → 2b7132c, #100928

Closed issues · 1

Closed#100479[Bug]: A *successful* `hermes update` leaves non-unit `serve` runtimes on pre-update code — and because they run cron tickers, every agent-mode cron job then fails with ImportError

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

Merged PRs: #100928
Closed issues: 1
Attempts: 2 PRs closed without merging
Fix link checked: 2 Sep 2026

For your agent

The same facts, typed.

cluster/100479.json
cluster/100479.md