# NousResearch/hermes-agent · Kanban worktree path and branch configuration

## Open now

- Nothing open on GitHub.

These issues and pull requests concern adding and fixing configuration of worktree paths and branches for kanban tasks, including placement control and routing worktrees to the correct repository.

## 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 #28462. Verify it addresses your case.
- **Recommended:** read PR #28462 (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: `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

- #26485: \[Feature\]: Support --workspace worktree:<path> + --branch for controlled kanban worktree placement

## Prior & competing PRs

- **#28462: feat(kanban): configure worktree paths and branches (#26496)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/kanban.py`, `hermes_cli/kanban_db.py`, `skills/devops/kanban-worker/SKILL.md`, `tests/hermes_cli/test_kanban_cli.py`, `tests/hermes_cli/test_kanban_db.py`, `website/docs/user-guide/features/kanban.md`
- **#26496: feat(kanban): configure worktree paths and branches**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `a7558cf27`, `#28462`

## Fix status

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