Cairn
NousResearch/hermes-agent

Kanban notification delivery bugs and features

Cluster 49190 · dashboard. Data as of

1 open item. Fix merged in #72177 on 26 Jul 2026. Check it covers your case.

The short answer

1open issue
0open PRs
7items grouped
Known?
Yes. 7 related items grouped here, 2 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 PR #72177. That is separate from the fix event.
Still open
1 issue and 0 PRs.

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 issues1

  • 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

3 PRs closed without merging

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

  • #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 · 2
  • 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.27: 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
dashboard
Merged PRs
#72177
Closed issues
2
Attempts
3 PRs closed without merging
Fix link checked
26 Jul 2026

For your agent

The same facts, typed.

cluster/49190.json
cluster/49190.md