Cairn
NousResearch/hermes-agent

Windows update gateway isolation and cross-OS fixes

Cluster 124659. Data as of

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

The short answer

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

These items address a bug where updating Hermes on Windows incorrectly stops gateways belonging to other Hermes installations, and include related fixes to scope gateway lifecycle to the current install and improve gateway recognition across operating systems.

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.

  • #124965 fix(gateway): recognise Hermes inline-bootstrap gateways on every OS (salvage #123331)

    merged to main

    files: gateway/status.py, hermes_cli/gateway_windows.py, hermes_cli/update_cmd_windows.py, hermes_cli/update_fleet_scope.py, tests/e2e/core/windows_update/_machine.py, tests/e2e/core/windows_update/test_gateway_across_update.py, tests/e2e/core/windows_update/test_update_spares_other_installs.py, tests/gateway/test_gateway_inline_bootstrap_identity.py, tests/hermes_cli/test_update_windows_cross_install_gateway.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · merged via another change 1

  • #124676 fix(update): scope Windows gateway lifecycle to current install · merged via another change → 60e531c, 46fba4c, #124965, #124962
  • #124962 fix(update): Windows update leaves other installs' gateways alone (salvage #124676) · done elsewhere → 46fba4c, 878d902, #124965
Closed issues · 1
  • Closed#124659Windows: hermes update force-stops the gateways of other Hermes installs on the same machine ("without profile mapping")
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
#124965
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
27 Sep 2026

For your agent

The same facts, typed.

cluster/124659.json
cluster/124659.md