Telegram DM topic notification routing fixes
Cluster 60600 · gateway. Data as of
Nothing open on GitHub. Fix merged in #72232 on 26 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #72232. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #72232. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple fixes addressing how notifications from kanban, cron, gateway, and background processes are routed and delivered to Telegram DM topics. Issues include missing reply anchors, incorrect routing paths, and lost metadata for private thread destinations.
Open issues0
Open PRs0
Fixes on record
-
#72191 fix(gateway): kanban wakes resume the creator's DM/thread session (salvage #58615 + #64113)
files:
contributors/emails/[redacted:email],gateway/kanban_watchers.py,gateway/run.py,gateway/session_context.py,gateway/slash_commands.py,hermes_cli/kanban.py,hermes_cli/kanban_db.py,tests/gateway/test_kanban_notifier.py,tools/kanban_tools.py -
#72232 fix(gateway): deliver kanban notifications to Telegram DM topics (salvage #60769 + #63927)
files:
gateway/kanban_watchers.py,gateway/run.py,gateway/slash_commands.py,hermes_cli/kanban_db.py,tests/conftest.py,tests/gateway/test_kanban_notifier.py,tests/gateway/test_session_env.py,tests/gateway/test_telegram_topic_mode.py,tests/hermes_cli/test_kanban_core_functionality.py,tests/hermes_cli/test_kanban_db_init.py,tests/hermes_cli/test_kanban_notify.py,tests/tools/test_kanban_tools.py,tools/kanban_tools.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#60769 fix(kanban): preserve Telegram DM topic notification metadata · merged via another change →
#72232,#63927,#72191
Closed issues · 1
- Closed#60600Kanban notifications fail in Telegram DM topics without reply anchor
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.50: 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