NousResearch/hermes-agent
Kanban profile discovery uses hardcoded Hermes root path
Cluster 19017. Data as of
Nothing open on GitHub. Fix merged in #19020 on 4 May 2026. Check it covers your case.
The short answer
0open issues
0open PRs
3items grouped
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #19020. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #19020. That is separate from the fix event. - Still open
- 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.
Open issues0
Open PRs0
Fixes on record
-
#19020 fix(kanban): profile discovery ignores HERMES_HOME in custom-root deployments
files:
hermes_cli/kanban_db.py,tests/hermes_cli/test_kanban_core_functionality.py
1 PR closed without merging
From the close comments: duplicate 1
-
#19030 fix(kanban): use get_default_hermes_root() for profile discovery · duplicate →
#19020,#19017
Closed issues · 1
- Closed#19017[Bug]: kanban init profile discovery hardcodes ~/.hermes/profiles instead of using get_default_hermes_root()
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.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
- Merged PRs
- #19020
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 4 May 2026