Cairn
NousResearch/hermes-agent

Kanban decomposed task assignee routing fixes

Cluster 114294. Data as of

Nothing open on GitHub. Fix merged in #114822 on 18 Sep 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 1 issue 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 resolved, deciding PR #114822. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and pull requests address a bug where decomposed child tasks in the Kanban dispatcher were incorrectly assigned to the dispatcher's own or 'private' profile instead of falling back to the root task's assignee. The work involves fixing routing logic to keep unroutable children associated with the correct profile.

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.

  • #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

2 PRs closed without merging

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

  • #114303 fix(kanban): fall back to the root task's assignee for unrouted decompose children · merged via another change → 957bf63, #114822, #114294, #114303
  • #114304 fix(kanban): keep unroutable decomposed children on the card's profile · superseded by another PR → #114303
Closed issues · 1
  • Closed#114294Kanban dispatcher spawns tasks on the 'private' profile instead of the task's assignee
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.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

Merged PRs
#114822
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
18 Sep 2026

For your agent

The same facts, typed.

cluster/114294.json
cluster/114294.md