Cairn

Kanban task workspace isolation bug fixes

NousResearch/hermes-agent · cluster 61911 · agent

Data as of

Nothing open on GitHub. Fix merged in #70143. Check it covers your case.

The short answer

0open issues
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 2 issues 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 PRs #70143, #70177. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address bugs where kanban tasks incorrectly shared worktree checkouts or workspace paths, including decomposed siblings, worker-created child tasks, and scratch children inheriting parent workspaces.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #70143 fix(kanban): worker-created child tasks get their own workspace

    merged to main

    files: contributors/emails/[redacted:email], hermes_cli/kanban_db.py, tests/tools/test_kanban_tools.py, tools/kanban_tools.py

  • #70177 fix(kanban): decomposed siblings stop sharing one worktree checkout

    merged to main

    files: hermes_cli/kanban_db.py, tests/hermes_cli/test_kanban_worktree_isolation.py

3 PRs closed without merging

From the close comments: merged via another change 2 · superseded by another PR 1

  • #61907 fix(kanban): stop decompose siblings sharing one worktree checkout · merged via another change → 65d42e3, #70177
  • #67570 fix(kanban): isolate worker-created child workspaces · merged via another change → 781968b, #70143
  • #67574 fix(kanban): scratch children no longer inherit parent workspace path · superseded by another PR → 781968b, #70143, #67570
Closed issues · 2
  • Closed#61911kanban: decompose siblings share one worktree checkout and run on each other's branches
  • Closed#67567kanban: worker-created scratch children inherit parent workspace path
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.26: the share of item 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.

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 Lab

At a glance

Subsystem
agent
Merged PRs
#70143, #70177
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
23 Jul 2026

For your agent

The same facts, typed.

cluster/61911.json
cluster/61911.md