NousResearch/hermes-agent

Kanban triage decomposition assignee/orchestrator ownership handling

Cluster 65026 · cron. Data as of 2026-10-26 12:29 UTC

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

open issue

open PRs

items grouped

Known?: Yes. 3 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: 1 issue and 0 PRs.

Next step: read #114822, then check whether your report is the one still open.

Read #114822 Pick up a Lab task

These items appear to concern how the kanban triage decomposition step picks the assignee for the root card and its child cards, including a report that --assignee / orchestrator_profile is ignored and resolves to 'default'. The two fix-style titles seem to address related ownership behavior (orchestrator overwriting the triage owner; children falling back to the root task's assignee), but the titles alone don't confirm outcomes.

Open issues1

Issue#65026decompose_triage_task ignores --assignee / orchestrator_profile; resolves root_assignee as 'default'

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

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 (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: 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.

cluster/65026.json
cluster/65026.md