Cairn
NousResearch/hermes-agent

Mixed path separators in hermes doctor output

Cluster 49497 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

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

Reports and fixes for hermes doctor displaying inconsistent POSIX and Windows path styles in .env messages. Changes normalize Hermes home path display to use forward slashes consistently.

Open issues1

  • Issue#49500hermes doctor shows mixed POSIX and Windows path style in .env message

Open PRs1

  • PR#49507fix(constants): render display_hermes_home tail with forward slashes

1 PR closed without merging

From the close comments: duplicate 1

  • #49974 fix(cli): normalize Hermes home display separators · duplicate → #49507, #49500
Closed issues · 1
  • Closed#49497hermes doctor shows mixed POSIX and Windows path style in .env message
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.39: 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
1
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/49497.json
cluster/49497.md