NousResearch/hermes-agent

Windows venv lock and gateway update handling

Cluster 75334 · apps/desktop. Data as of 2026-10-27 11:58 UTC

2 open items. Fix merged in #75881 on 1 Aug 2026. 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 #75881. 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: 0 issues and 2 PRs.

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

Read #75881 Pick up a Lab task

These issues and fixes address how the Windows desktop updater handles venv locks held by gateway processes, shifting behavior from aborting updates to pausing, allowing handoff, or selectively terminating gateway processes. The work is scoped to Windows-specific update and install flows.

Open issues0

No open issues.

Open PRs2

PR#57852fix(update): ignore Windows system venv holder noise
PR#75380fix(desktop): allow updater handoff for gateway-only venv locks

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#75881 fix(update): let Windows desktop updates pause gateway processes instead of aborting

merged to main

files: hermes_cli/_scan_venv_blockers.py, hermes_cli/main.py, hermes_cli/update_cmd.py, tests/hermes_cli/test_gateway.py, tests/hermes_cli/test_scan_venv_blockers.py, tests/hermes_cli/test_update_concurrent_quarantine.py

1 PR closed without merging

From the close comments: superseded by another PR 1

#46726 fix(install): kill venv-resident gateway before recreating venv on Windows · superseded by another PR → #52044

Closed issues · 1

Closed#75334Bug: Desktop self-update always aborts when a non-Desktop-owned gateway process holds the venv lock (Windows)

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

For your agent

The same facts, typed.

cluster/75334.json
cluster/75334.md