Windows worktree cleanup blocked by worker directory lock
Cluster 112425. Data as of
Nothing open on GitHub. Fix merged in #113073 on 16 Sep 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 #113073. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #113073. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a Windows-specific issue where kanban worktree cleanup cannot remove the worktree because the worker's current working directory is inside it. Fixes involve stepping out of or releasing the worktree directory before attempting removal.
Open issues0
Open PRs0
Fixes on record
-
#113073 fix(kanban): worktree cleanup steps out of the worktree before removing it on Windows (#112425, salvage #112429)
files:
hermes_cli/kanban_db_workspace.py,tests/hermes_cli/test_kanban_worktree_teardown.py
1 PR closed without merging
From the close comments: closed without comment 1
- #112429 fix(kanban): release worker cwd before worktree cleanup · closed without comment
Closed issues · 1
- Closed#112425Windows: kanban worktree cleanup empties the worktree but cannot remove it when the worker's cwd is inside it
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
- #113073
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 16 Sep 2026