Cairn
NousResearch/hermes-agent

Fix managed Node resolution under named profiles

Cluster 75347 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues 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.

These items address a bug where find_node_executable() fails to locate a managed Node installation because Node is installed at the machine level but resolution is scoped to the named profile. The fix and related report all concern the same resolution path mismatch.

Open issues1

  • Issue#75347find_node_executable() returns None under any named profile — managed Node is machine-level, resolution is profile-scoped

Open PRs1

  • PR#75357fix: resolve managed Node from machine-level home under named profiles

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #113590 fix(node): resolve managed Node from machine-level home under named profiles · superseded by another PR → #75357
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
1 PR closed without merging

For your agent

The same facts, typed.

cluster/75347.json
cluster/75347.md