Cairn
NousResearch/hermes-agent

Telegram DM topic message routing fixes

Cluster 27139 · gateway. Data as of

Nothing open on GitHub. Fix merged in #27302 on 17 May 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 #27302. 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.

Multiple fixes addressing a bug where messages intended for specific Telegram DM topics were incorrectly routed to the wrong topic or leaked to All Messages, particularly during synthetic or queued notification events.

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.

  • #27302 Batch salvage group 3: 9 low-risk new-contributor PRs (custom-providers/non-vision-strip/telegram-dm-topic/cron-isolation/etc)

    merged to main

    files: cron/scheduler.py, gateway/run.py, hermes_cli/config.py, hermes_cli/goals.py, hermes_cli/kanban_db.py, hermes_cli/model_switch.py, run_agent.py, scripts/check-windows-footguns.py, scripts/release.py, tests/agent/test_anthropic_adapter.py, tools/code_execution_tool.py, tools/environments/local.py, tools/process_registry.py

2 PRs closed without merging

From the close comments: merged via another change 2

  • #27114 fix(gateway): synthetic/queued messages routed to wrong Telegram DM topic · merged via another change → #27302
  • #27937 fix(telegram): route resumed DM topic sends directly · merged via another change → #24004
Closed issues · 1
  • Closed#27139Telegram DM topic messages leak to All Messages on synthetic events
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
#27302
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
17 May 2026

For your agent

The same facts, typed.

cluster/27139.json
cluster/27139.md