NousResearch/hermes-agent

Kanban scope and gateway event routing fixes

Cluster 93851. Data as of 2026-10-30 11:57 UTC

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

open issues

open PRs

items grouped

Known?: Yes. 3 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #105356. 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: Nothing open on GitHub.

Next step: read #105356, then check it covers your case.

Read #105356 Pick up a Lab task

These members address a bug where kanban notifier wake turns ran outside the correct profile's runtime scope, causing Slack messages to be sent via the wrong bot, and a related fix ensuring heartbeat and completion events resume the correct owning conversation.

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.

#105356 fix(gateway): heartbeat and completion events resume the owning conversation

merged to main

files: evals/gateway_completion/README.md, evals/gateway_completion/delivery_lifecycle.py, evals/heartbeat_idle_wire.py, gateway/AGENTS.md, gateway/kanban_watchers_notifier.py, gateway/platforms/base.py, gateway/platforms/event.py, gateway/run.py, gateway/run_busy.py, gateway/run_goals.py, gateway/run_heartbeat_acceptance.py, gateway/run_heartbeat_restore.py, gateway/run_notifications.py, gateway/run_startup.py, gateway/run_turn.py, gateway/session_context.py, gateway/session_recovery.py, gateway/slash_commands.py, gateway/wake.py, hermes_cli/kanban.py (+33 more)

1 PR closed without merging

From the close comments: done elsewhere 1

#93863 fix(kanban): run wake turns under the target profile's runtime scope · done elsewhere → 4810074, #105356

Closed issues · 1

Closed#93851[Bug]: kanban notifier wake turns run without profile secret scope under multiplex — in-turn Slack sends go out via the wrong bot (channel_not_found)

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

Merged PRs: #105356
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/93851.json
cluster/93851.md