Kanban worker-created child tasks and workspace path inheritance
Cluster 67567 · agent. 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. 4 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
resolved, deciding PR #70143. That is separate from the fix event. - Still open
- Nothing open on GitHub.
All four members concern kanban child tasks created by workers and whether they share the parent's workspace path or get their own. Titles suggest a change toward isolated or separate child workspaces, but the titles alone do not show the outcome or status.
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
2 PRs closed without merging
From the close comments: merged via another change 1 · superseded by another PR 1
Closed issues · 1
- Closed#67567kanban: worker-created scratch children inherit parent workspace path
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.50: 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
- agent
- Merged PRs
- #70143
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 23 Jul 2026