Secondary-profile skill dispatch routing bug and fix
Cluster 110695. Data as of
Nothing open on GitHub. Fix merged in #111079 on 14 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111079. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111079. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items concern a bug where skill commands tied to secondary profiles cannot be looked up during dispatch, and a related fix scoping skill dispatch to the session profile. A broader multiplex gateway item also touches secondary-profile skill dispatch alongside other gateway concerns.
Open issues0
Open PRs0
Fixes on record
-
#111079 Multiplex gateway: cron ticker survives startup and is respawned, Discord-thread Kanban subs deliver under profile_routes, secondary-profile skills dispatch (#111010, #110919, #110695; salvage #111034, #110928, #110698)
files:
cron/scheduler_provider.py,cron/scheduler_thread.py,gateway/kanban_watchers_notifier.py,gateway/run.py,hermes_cli/kanban.py,hermes_cli/kanban_db_notify.py,hermes_cli/kanban_parser.py,tests/cron/test_ticker_startup_survival.py,tests/gateway/test_kanban_routed_transport.py,tests/hermes_cli/test_kanban_notify.py,tests/tui_gateway/test_protocol.py,tui_gateway/methods_tools.py,website/docs/user-guide/features/kanban.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#110698 fix(gateway): scope skill dispatch to session profile · merged via another change →
23ef640,4c306e9,#111079
Closed issues · 1
- Closed#110695[Bug]: command.dispatch cannot invoke secondary-profile skills — _is_profile_skill_command routes them, _dispatch_skill cannot resolve them
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.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 LabAt a glance
- Merged PRs
- #111079
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 14 Sep 2026