Cairn

Kanban dispatch claim scoping per home

NousResearch/hermes-agent · cluster 110995

Data as of

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

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #111386. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #111386. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address a bug where homes on a shared Kanban board could incorrectly claim cards assigned to other homes, and introduce a per-home dispatch allowlist (kanban.dispatch_profiles) to scope claim eligibility correctly.

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.

  • #111386 fix(kanban): homes with kanban.dispatch_profiles no longer claim other homes' default cards on a shared board (#110995, salvage #111004)

    merged to main

    files: hermes_cli/config_defaults.py, hermes_cli/kanban_db_dispatch.py, tests/hermes_cli/test_kanban_dispatch_claim_allowlist.py, website/docs/user-guide/features/kanban.md

3 PRs closed without merging

From the close comments: closed without comment 1 · partial fix 1 · superseded by another PR 1

  • #110997 fix(kanban): scope dispatch claims to current home · closed without comment
  • #111004 fix(kanban): per-home dispatch claim allowlist for shared boards (#110995) · superseded by another PR → #111386, #110995, #111900
  • #111206 feat(kanban): home-scoped dispatch allowlist (kanban.dispatch_profiles) · partial fix → #111386, #111004, #110995
Closed issues · 1
  • Closed#110995Kanban dispatcher claims across homes on a shared board: profile_exists("default") is unconditionally True, so every home can claim default-assigned cards
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.40: 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
#111386
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.

cluster/110995.json
cluster/110995.md