Cairn
NousResearch/hermes-agent

Kanban scratch workspace_path isolation in decompose

Cluster 103303 · hermes cli. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

These items concern a bug where decomposed sibling and child tasks incorrectly share or inherit the root task's workspace_path during triage decomposition, and fixes to ensure each scratch task gets an isolated path.

Open issues1

  • Issue#103303kanban: decompose_triage_task lets scratch siblings inherit the root's workspace_path, so concurrent workers share one directory

Open PRs1

  • PR#103325fix(kanban): scratch decompose children must not inherit a claimed root's workspace_path

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #103628 fix(kanban): scratch decompose siblings must not share the root's workspace_path · superseded by another PR → #103325, #103303
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.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
hermes cli
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/103303.json
cluster/103303.md