Kanban worktree isolation per task or subtask
Cluster 53983 · cron. Data as of
Nothing open on GitHub. Fix merged in #70143 on 23 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #70143. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes concern a bug where Kanban tasks or subtasks incorrectly share or inherit worktree paths rather than each receiving their own isolated worktree. Multiple related fixes address workspace assignment in different scenarios.
Open issues0
Open PRs0
Fixes on record
-
#70143 fix(kanban): worker-created child tasks get their own workspace
files:
contributors/emails/[redacted:email],hermes_cli/kanban_db.py,tests/tools/test_kanban_tools.py,tools/kanban_tools.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#54006 fix(kanban): give each subtask its own worktree instead of inheriting parent path (#53983) · superseded by another PR →
781968b,#70143,#53983,#61911,#61907
Closed issues · 1
- Closed#53983[Bug]: Kanban worktree mode is not working for multiple tasks
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
- Subsystem
- cron
- Merged PRs
- #70143
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 23 Jul 2026