Kanban auto-subscribe notification routing across profiles
NousResearch/hermes-agent · cluster 19479 · cron
Data as of
Nothing open on GitHub. Fix merged in #72241. Check it covers your case.
The short answer
- Known?
- Yes. 9 related items grouped here, 4 issues already closed.
- Fix event
- A fix was merged to main in PR #72241. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
partially resolved, deciding PRs #19718, #72241. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern auto-subscribing chats or CLI sessions to kanban task notifications on creation, and fixing notification routing bugs where the wrong profile, gateway bot, or agent receives or sends those notifications in multi-profile setups.
Open issues0
Open PRs0
Fixes on record
-
#72241 fix(kanban): profile-correct notification ownership and routing (salvage #57995, #56589, #62380, #69181)
files:
gateway/kanban_watchers.py,hermes_cli/kanban_db.py,tests/gateway/test_kanban_notifier.py,tests/gateway/test_multiplex_profile_authz.py,tests/hermes_cli/test_kanban_db.py,tests/tools/test_kanban_tools.py,tools/kanban_tools.py -
#19718 feat(kanban): auto-subscribe gateway chat on tool-driven kanban_create
files:
tests/tools/test_kanban_tools.py,tools/kanban_tools.py
3 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1 · merged via another change 1
-
#35549 feat(kanban): auto-subscribe CLI session on task create + --cli flag · done elsewhere →
f8d8f04,#19479 -
#57995 fix: scope kanban auto-subscriptions to active profile · merged via another change →
#72241,#57993 -
#66408 fix(kanban): bind auto-subscriptions to active profile · duplicate →
#57995
Closed issues · 4
- Closed#19479feat(kanban): kanban_create tool should auto-subscribe originating gateway chat to notifications
- Closed#39738kanban_create tool: missing notifier_profile in auto-subscribe causes notification from wrong gateway bot
- Closed#56802kanban notify/wake in multi-profile gateways: notifier coupled to dispatch_in_gateway, notifier_profile mis-resolves to 'default', wake targets dispatcher's agent instead of creator
- Closed#57993Kanban auto-subscribe can leak notifications across profiles
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.18: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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