{"repo":"NousResearch/hermes-agent","public_id":"140682","display_label":"Windows gateway launcher non-ASCII path handling","summary":"The members all concern the gateway's Windows launcher and preserving Unicode or localized (non-ASCII) paths, such as a non-ASCII HERMES_HOME. One is a bug report about a Scheduled Task gateway not starting, with mention of BOM-less UTF-8 launchers and a strict-UTF-8 .vbs reader; the other two are fix-titled changes on the same area.","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":140682,"title":"[Bug]: Windows: Scheduled Task gateway silently never starts on a non-ASCII HERMES_HOME (BOM-less UTF-8 launchers, plus the strict-UTF-8 .vbs reader a writer-only fix would break)","url":null,"state":"open"},{"kind":"pr","number":140693,"title":"fix(gateway): preserve localized Windows launcher paths","url":null,"state":"open","close_reason":{"category":"silent_close","implication":"active"},"merged":false},{"kind":"pr","number":140695,"title":"fix(gateway): preserve Unicode Windows launcher paths and identity","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}