# NousResearch/hermes-agent · Telegram gateway routing and message leakage fixes

## Open now

- Nothing open on GitHub.

These items address bugs in the Telegram gateway involving out-of-context replies, duplicate messages, tool-trace leakage, stale generation responses, and DM-topic routing. The work is focused on correcting message handling and routing correctness in the Telegram integration.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 0 merged PR(s), 2 PR(s) closed without merging.
- No fix has been merged to main; one or more PRs were attempted (see below).
- **Recommended:** review the prior/competing PR(s) below. A fix was attempted but not merged; your case may extend or revive that work.

## 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.67`: 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

- #37555: \[Bug\]: Telegram gateway replies out-of-context (tool trace leakage + duplicated messages)

## Prior & competing PRs

- **#38732: fix(gateway): prevent Telegram duplicate messages and tool-trace leakage (#36965 #37555)**. closed without merge · fix tier `suggested`
  - maintainer direction: category `partial_fix`; implication `needs_llm`; refs `#36965`, `#37555`
  - _suggested-tier fix detail withheld; re-request with `?tier=all` to include it._
- **#37698: fix(gateway): drop stale generation final responses**. closed without merge
  - maintainer direction: category `superseded_by_pr`; implication `superseded`; refs `#38732`

## Fix status

- No merged fix on record.
- Subsystem: `gateway`