Kanban notification delivery bugs and features

NousResearch/hermes-agent · cluster 31901 · agent

Data as of 2026-10-22 12:15 UTC

2 open items. Fix merged in #72177. Check it covers your case.

open issues

open PRs

items grouped

Known?: Yes. 14 related items grouped here, 4 issues already closed.
Fix event: A fix was merged to main in PR #72177. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this partially resolved, deciding PRs #72177, #72236. That is separate from the fix event.
Still open: 2 issues and 0 PRs.

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

Read #72177 Pick up a Lab task

This cluster covers work on Kanban task event notification delivery — including blocked or missed sends, TUI/desktop session gaps, subscription polling issues, decomposed task handling, and proposals to generalize the notification system across surfaces.

Open issues2

Issue#35417[Feature]: Kanban task terminal-event callbacks for async orchestration (TUI/WebUI + coordinator workflows)
Issue#49190[Feature]: Generalize Kanban notifications into an event substrate — any-surface subscribers + delivery-adapter registry

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#72177 fix(tui): deliver kanban notify subscriptions to TUI/desktop sessions (salvage #66435)

merged to main

files: tests/tui_gateway/test_kanban_notify_poller.py, tui_gateway/server.py
#72236 fix(gateway): isolate kanban notifier failures + cursor snap at creation (salvage #59278, #62712, #63001)

merged to main

files: contributors/emails/[redacted:email], gateway/authz_mixin.py, gateway/kanban_watchers.py, hermes_cli/kanban_db.py, tests/gateway/test_kanban_notifier.py, tests/gateway/test_kanban_notifier_zero_sub_gate.py, tests/gateway/test_multiplex_profile_authz.py, tests/hermes_cli/test_kanban_core_functionality.py, tests/hermes_cli/test_kanban_count_notify_subs.py, tests/hermes_cli/test_kanban_notify.py, tests/tui_gateway/test_kanban_notify_poller.py
#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)

5 PRs closed without merging

From the close comments: merged via another change 3 · done elsewhere 2

#31902 fix(kanban): preserve notifications and workspace for decomposed tasks · done elsewhere → 4810074, #105356
#59278 fix(gateway): isolate per-subscription failures in kanban notifier · merged via another change → #72236, #59269
#59963 fix(tui): poll kanban_notify_subs for task event delivery to TUI sessions · done elsewhere → badb240, 6247712, #72177, #66435, #60085
#60085 fix(tui): deliver kanban notify subscriptions to TUI/desktop sessions · merged via another change → #66435
#66435 fix(tui): deliver Kanban notifications to TUI sessions · merged via another change → badb240, 6247712, #72177

Closed issues · 4

Closed#31901[Bug]: Kanban notifications can be lost for failed sends and decomposed child tasks
Closed#59269Kanban notifier jams permanently on one bad delivery — masks the real error and blocks all notifications
Closed#59890[Bug] Kanban task event notifications never delivered — all 18 subscriptions have last_event_id=0
Closed#59960[Bug] TUI kanban notifications never delivered — poller only watches process completions, not kanban_notify_subs

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.12: 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: agent
Merged PRs: #72177, #72236, #105356
Closed issues: 4
Attempts: 5 PRs closed without merging
Fix link checked: 7 Sep 2026

For your agent

The same facts, typed.

cluster/31901.json
cluster/31901.md