NousResearch/hermes-agent

Skip gateway cold-start during desktop serve on Windows

Cluster 76129 · apps/desktop. Data as of 2026-10-23 11:54 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 5 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #92698. 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.

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

Read #92698 Pick up a Lab task

These issues and PRs address a bug where the Windows Hermes update process unnecessarily cold-starts a standalone gateway when the desktop app (hermes serve) is already running as the runtime. The work involves detecting this condition and skipping the redundant cold-start.

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.

#92698 fix(update): Windows update no longer spawns a rogue gateway beside Desktop (#76129, salvage #76745)

merged to main

files: hermes_cli/main.py, hermes_cli/update_cmd.py, tests/hermes_cli/test_desktop_lifecycle_windows_live.py, tests/hermes_cli/test_windows_gateway_cold_start_desktop_lifecycle.py

3 PRs closed without merging

From the close comments: merged via another change 1 · other 2

#76173 fix(update): skip gateway cold-start when desktop serve is running · other
#76708 fix(update): skip gateway cold-start when desktop backend is running (#76129) · other → b14d75f, #76173
#76745 fix(update): skip Windows gateway cold-start when Desktop owns lifecycle · merged via another change → f406777, #92698, #90778, #92091

Closed issues · 1

Closed#76129[Bug]: Windows hermes update cold-starts a standalone gateway after every update when the desktop app (hermes serve) is the runtime

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

Subsystem: apps/desktop
Merged PRs: #92698
Closed issues: 1
Attempts: 3 PRs closed without merging
Fix link checked: 23 Aug 2026

For your agent

The same facts, typed.

cluster/76129.json
cluster/76129.md