# NousResearch/hermes-agent · Kanban profile discovery uses hardcoded Hermes root path

## Open now

- Nothing open on GitHub.

These issues and fixes address a bug where kanban profile discovery hardcodes ~/.hermes/profiles instead of respecting HERMES_HOME or calling get_default_hermes_root(). The work centers on correcting path resolution for non-standard Hermes deployments.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #19020. Verify it addresses your case.
- **Recommended:** read PR #19020 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-19020`. 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

- #19017: \[Bug\]: kanban init profile discovery hardcodes ~/.hermes/profiles instead of using get_default_hermes_root()

## Prior & competing PRs

- **#19020: fix(kanban): profile discovery ignores HERMES_HOME in custom-root deployments**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/kanban_db.py`, `tests/hermes_cli/test_kanban_core_functionality.py`
- **#19030: fix(kanban): use get_default_hermes_root() for profile discovery**. closed without merge
  - maintainer direction: category `duplicate_of`; implication `duplicate`; refs `#19020`, `#19017`

## Fix status

- Merged to main in PR #19020 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-04`.