Kanban auto-decompose ignores assignee containment settings

NousResearch/hermes-agent · cluster 62985 · cron

Data as of

4 open items. Fix merged in #114822. Check it covers your case.

The short answer

2open issues
2open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 0 issues already closed.
Fix event
A fix was merged to main in PR #114822. 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
2 issues and 2 PRs.

These items concern a bug where the auto-decompose triage task ignores configured assignee or orchestrator profile settings, silently overwriting or bypassing deliberate non-spawnable assignee containment. Multiple fixes and reports address the same underlying containment bypass.

Open issues2

  • Issue#62985Kanban auto-decompose silently reassigns and launches tasks whose assignee is deliberately non-spawnable (containment bypass)
  • Issue#65026decompose_triage_task ignores --assignee / orchestrator_profile; resolves root_assignee as 'default'

Open PRs2

  • PR#62994fix(cron): honor non-spawnable assignee containment in kanban auto-decompose
  • PR#65952fix(kanban): keep decomposition inert for parked triage tasks

Fixes on record

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

  • #114822 fix(kanban): decomposed children and the root card fall back to the root task's assignee, never the dispatcher's own profile (#114294, salvage #114303)

    merged to main

    files: hermes_cli/kanban_decompose.py, plugins/kanban/dashboard/plugin_api.py, tests/hermes_cli/test_kanban_decompose.py, website/docs/user-guide/features/kanban.md

1 PR closed without merging

From the close comments: superseded by another PR 1

  • #65117 fix: stop configured orchestrator overwriting triage owner · superseded by another PR → 957bf63, #114822, #114294, #114303
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.29: 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
cron
Merged PRs
#114822
Closed issues
0
Attempts
1 PR closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.