NousResearch/hermes-agent

gateway --replace race and respawn-storm fixes

Cluster 119807. Data as of 2026-10-27 11:58 UTC

Nothing open on GitHub. Fix merged in #120122 on 23 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 #120122. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this resolved, deciding PR #120122. That is separate from the fix event.
Still open: Nothing open on GitHub.

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

Read #120122 Pick up a Lab task

These items concern bugs where the gateway's --replace flag could start a second gateway instance alongside an existing standalone owner, trigger respawn storms, or deadlock on a stale systemd drop-in. The group covers both the bug reports and associated fixes for these related race and targeting issues.

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.

#120122 fix(gateway): --replace no longer starts a second gateway on a lost lock race, respawn-storms beside a standalone owner, or deadlocks on the stale systemd drop-in (#119837, #119807, #119467)

merged to main

files: gateway/host_attach.py, gateway/run.py, hermes_cli/gateway_service_unit.py, tests/gateway/test_host_attach_lifecycle.py, tests/gateway/test_host_gateway_lock_refusal.py, tests/hermes_cli/test_systemd_replace_dropin.py, website/docs/user-guide/multi-profile-gateways.md

1 PR closed without merging

From the close comments: merged via another change 1

#119808 fix(gateway): --replace starts beside another profile's standalone owner · merged via another change → 1a4da74, #120122

Closed issues · 1

Closed#119807--replace units respawn-storm on a one-gateway-per-profile host: decide() targets another profile's standalone owner

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: #120122
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 23 Sep 2026

For your agent

The same facts, typed.

cluster/119807.json
cluster/119807.md