Cairn
NousResearch/hermes-agent

Windows gateway launcher non-ASCII path handling

Cluster 140682 · 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.

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.

Open issues1

  • Issue#140682[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)

Open PRs2

  • PR#140693fix(gateway): preserve localized Windows launcher paths
  • PR#140695fix(gateway): preserve Unicode Windows launcher paths and identity
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/140682.json
cluster/140682.md