NousResearch/hermes-agent

Windows update hand-off kills gateway, suppresses cold-start

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

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

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

Read #110020 Pick up a Lab task

A bug where the Windows Desktop self-update hand-off terminates the running gateway and the subsequent update process suppresses the cold-start, leaving the bot silently offline. Several fix attempts address preserving the cold-start plan across the update hand-off sequence.

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.

#110020 fix(update): Windows update cold-starts the gateway when the Desktop-owned one is dead (#109538, salvage #109545)

merged to main

files: contributors/emails/[email protected], hermes_cli/gateway_windows.py, hermes_cli/update_cmd_windows.py, tests/hermes_cli/test_gateway_start_attestation.py, tests/hermes_cli/test_windows_gateway_cold_start_desktop_lifecycle.py

2 PRs closed without merging

From the close comments: merged via another change 1 · partial fix 1

#109545 fix(update): keep the Windows cold-start plan for a dead attested gateway (#109538) · merged via another change → 7e76415, #110020, #109538
#109591 fix(update): preserve Windows gateway cold-start during Desktop update hand-off (#109538) · partial fix → aa1ec19, #109545

Closed issues · 1

Closed#109538[Bug]: Windows: Desktop self-update hand-off kills the running gateway, then the update suppresses the cold-start - bot silently offline until manual start

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

For your agent

The same facts, typed.

cluster/109538.json
cluster/109538.md