# NousResearch/hermes-agent · Telegram DM topic message routing fixes

## Open now

- 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.

## TL;DR

- 4 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 2 PR(s) closed without merging.
- A fix was merged to main in PR #27302. Verify it addresses your case.
- **Recommended:** read PR #27302 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.50`: the share of member 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.

## Closed / duplicate issues

- #27139: Telegram DM topic messages leak to All Messages on synthetic events

## Prior & competing PRs

- **#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 · fix tier `verified`
  - maintainer direction: category `merged`
  - 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`
- **#27114: fix(gateway): synthetic/queued messages routed to wrong Telegram DM topic**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#27302`
- **#27937: fix(telegram): route resumed DM topic sends directly**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `#24004`

## Fix status

- Merged to main in PR #27302 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-05-17`.
- Subsystem: `gateway`