NousResearch/hermes-agent

Kanban dispatcher failing to locate the hermes binary

Cluster 24491 · hermes cli. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

The members concern how the kanban gateway dispatcher resolves the hermes executable: one issue reports shutil.which('hermes') returning None even though the binary is on PATH. Two pull requests propose changes to resolution logic (a hardcoded fallback path for symlink environments, and an importability check for hermes_cli before returning the module form).

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #24517 fix: add hardcoded fallback path in _resolve_hermes_bin for symlink environments · done elsewhere → 62b1c74
  • #24528 fix(kanban): _resolve_hermes_argv checks hermes_cli importability before returning module form · other
Closed issues · 1
  • Closed#24491kanban: shutil.which('hermes') returns None in gateway dispatcher despite binary on PATH
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
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.