Cairn

Telegram reply media not forwarded to agent

NousResearch/hermes-agent · cluster 22249 · gateway

Data as of

Nothing open on GitHub. Fix merged in #46107. Check it covers your case.

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 3 issues already closed.
Fix event
A fix was merged to main in PR #46107. 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.

These issues and PRs address a bug where photos or other media attachments from replied-to Telegram messages are not passed along to the agent. Multiple fixes and reports cover downloading and attaching that reply media for agent vision.

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.

  • #46107 fix(gateway): include replied-to media attachments

    merged to main

    files: gateway/platforms/telegram.py, plugins/platforms/discord/adapter.py, tests/e2e/test_discord_adapter.py, tests/gateway/test_telegram_group_gating.py

2 PRs closed without merging

From the close comments: done elsewhere 1 · superseded by another PR 1

  • #22251 fix(telegram): download reply-to-message photo for agent vision · done elsewhere → efbe163, #46107
  • #37971 fix(telegram): attach media from replied messages · superseded by another PR → efbe163, #46107
Closed issues · 3
  • Closed#22249fix(telegram): Reply-to-message photo not forwarded to agent
  • Closed#22250fix(telegram): Reply-to-message photo not forwarded to agent
  • Closed#37970Telegram replies to media do not attach the replied image or document
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.34: 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
#46107
Closed issues
3
Attempts
2 PRs closed without merging
Fix link checked
14 Jun 2026

For your agent

The same facts, typed.

cluster/22249.json
cluster/22249.md