Cairn

Windows gateway respawn uses wrong interpreter after update

NousResearch/hermes-agent · cluster 106489 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

A bug where the Windows update process relaunches the gateway using the base interpreter instead of the virtual environment interpreter, causing missing module errors. The members cover the bug report and related fixes targeting argv and venv interpreter binding.

Open issues1

  • Issue#106489[Bug]: Windows update exits 1 - post-update gateway relaunch replays the uv venv's base interpreter (No module named yaml)

Open PRs2

  • PR#106491fix(update): rebind the Windows gateway respawn to the install venv interpreter
  • PR#122144fix(windows): respawn gateway on the venv interpreter when captured argv leads with the base interpreter
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

Subsystem
hermes cli
Closed issues
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/106489.json
cluster/106489.md