Doctor misreports launcher path on PM installs
NousResearch/hermes-agent · cluster 124050 · environments
Data as of
3 open items. Fix attempted, not merged.
The short answer
1open issue
2open PRs
4items grouped
- Known?
- Yes. 4 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 2 PRs.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskA bug causes the doctor command to permanently report the Hermes entry point as not found on PM installs, because it checks a workspace path where the launcher is never staged. The fixes address launcher staging into the workspace and correct the path resolution logic used by doctor.
Open issues1
- Issue#124050[Bug]: hermes doctor permanently reports "Hermes entry point not found (<gen>/workspace/hermes)" on PM installs — the staged workspace never contains the launcher
Open PRs2
1 PR closed without merging
From the close comments: other 1
-
#124122 fix(doctor): resolve the launcher PM installs actually run instead of the never-staged workspace path (fixes #124050) · other →
#124050
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- environments
- Closed issues
- 0
- Attempts
- 1 PR closed without merging