Inbound Telegram media (photos and documents) is dropped by the receive path #1551

Closed
opened 2026-10-27 13:40:51 +00:00 by sam · 0 comments
Owner

The adapter can send media and the message type carries a media field, but nothing in the inbound path stores or forwards an incoming photo or document, so the agent receives the message with no media. This is a receive-path gap, not a send-path one.

Acceptance criteria

An inbound photo and an inbound document each reach the agent with the media accessible, plus a degrade path for an unsupported or oversized type; red-first tests

Close reason

Closed


Imported from beads archie-core-ro0c · GitHub #1465 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02

The adapter can send media and the message type carries a media field, but nothing in the inbound path stores or forwards an incoming photo or document, so the agent receives the message with no media. This is a receive-path gap, not a send-path one. ### Acceptance criteria An inbound photo and an inbound document each reach the agent with the media accessible, plus a degrade path for an unsupported or oversized type; red-first tests ### Close reason Closed --- _Imported from beads `archie-core-ro0c` · GitHub #1465 · type bug · priority P2 · created 2026-10-02 · closed 2026-10-02_
sam added the mediumbug labels 2026-10-27 13:40:51 +00:00
sam self-assigned this 2026-10-27 13:40:51 +00:00
sam closed this issue 2026-10-27 13:40:51 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1551