Cairn
NousResearch/hermes-agent

Telegram topic lobby blocking internal gateway events

Cluster 63911 · gateway. Data as of

Nothing open on GitHub. Fix merged in #72232 on 26 Jul 2026. Check it covers your case.

The short answer

0open issues
0open PRs
4items grouped
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 unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

A bug was identified where Telegram DM topic mode silently drops kanban wake events lacking a thread_id, and a fix was introduced to let internal events bypass the topic lobby gate. A related refactor centralizes port-binding constants and profile validation in the gateway.

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.

  • #72232 fix(gateway): deliver kanban notifications to Telegram DM topics (salvage #60769 + #63927)

    merged to main

    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

2 PRs closed without merging

From the close comments: merged via another change 2

  • #63927 fix(gateway): let internal events bypass Telegram topic lobby · merged via another change → #72232, #60769
  • #64005 refactor(gateway): centralize port-binding platform constants and multiplex profile validation · merged via another change → #62801, #63911, #65700, #62803
Closed issues · 1
  • Closed#63911Telegram DM topic mode: root-lobby gate silently swallows kanban wake events with no thread_id — completions never processed
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.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
gateway
Merged PRs
#72232
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
26 Jul 2026

For your agent

The same facts, typed.

cluster/63911.json
cluster/63911.md