{"repo":"NousResearch/hermes-agent","public_id":"106489","display_label":"Windows gateway respawn uses wrong interpreter after update","summary":"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.","subsystem":"hermes_cli","counts":{"members":3,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":2},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.6666666666666666},"fix_edges":[],"members":[{"kind":"issue","number":106489,"title":"[Bug]: Windows update exits 1 - post-update gateway relaunch replays the uv venv's base interpreter (No module named yaml)","url":null,"state":"open"},{"kind":"pr","number":106491,"title":"fix(update): rebind the Windows gateway respawn to the install venv interpreter","url":null,"state":"open","close_reason":{"category":"wontfix_bydesign","implication":"wontfix"},"merged":false},{"kind":"pr","number":122144,"title":"fix(windows): respawn gateway on the venv interpreter when captured argv leads with the base interpreter","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}