# NousResearch/hermes-agent · Telegram sibling-bot message routing and observation gaps

## Open now

- Nothing open on GitHub.

These items address cases where Telegram messages matching wake-words or quote-replies from sibling bots are incorrectly dropped or misrouted, falling through both dispatch and observation paths. The work focuses on ensuring such messages reach the intended context rather than being silently discarded.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #116797. Verify it addresses your case.
- **Recommended:** read PR #116797 (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: `resolved` · deciding PR(s): `pr-116797`. 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

- #115119: \[Bug\]: Telegram bot message matching mention_patterns can be dropped from both dispatch and observation paths

## Prior & competing PRs

- **#116797: fix(telegram): sibling-bot wake-word and quote-reply messages land in observed context instead of vanishing (#115119, salvage #115156)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `plugins/platforms/telegram/adapter.py`, `tests/gateway/test_telegram_group_gating.py`
- **#115156: fix(telegram): observe sibling-bot wake-word messages dropped by the bot-to-bot gate**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `e7509fa1a4d`

## Fix status

- Merged to main in PR #116797 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-20`.