# NousResearch/hermes-agent · Kanban dispatcher failing to locate the hermes binary

## Open now

- 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).

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #24491: kanban: shutil.which('hermes') returns None in gateway dispatcher despite binary on PATH

## Prior & competing PRs

- **#24517: fix: add hardcoded fallback path in _resolve_hermes_bin for symlink environments  **. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `62b1c74cbc62cde1204fecc3c2682d312b995876`
- **#24528: fix(kanban): _resolve_hermes_argv checks hermes_cli importability before returning module form**. closed without merge
  - maintainer direction: category `uncategorized`; implication `needs_llm`

## Fix status

- No merged fix on record.
- Subsystem: `hermes_cli`