/rc Telegram bridge: photos are silently dropped (no image/attachment relay) #1015

Summary

Sending a photo (or any other attachment) to a /rc session over Telegram relays nothing at all: no turn, no placeholder, no notice. Only text messages reach the session. Reproduced with the Desktop app's Remote control (its relay wrapper is identical to the CLI bridge's).

Steps to reproduce

1. Start a session and connect it with /rc to Telegram.
2. From the Telegram chat, send a photo or a screenshot.
3. Watch the session: nothing is relayed. Plain text sent to the same chat appears normally.

Expected behavior

Deliver the attachment to the session — e.g. download it via the Bot API (getFile, ≤20 MB) into the session's working directory and reference the local path in the relayed prompt, so vision-capable models can read it (read_file already shows images to vision models). At minimum: post a short "attachments aren't supported" notice and forward the message caption if present. Right now the failure is completely silent — both the user and the agent believe the photo was delivered.

Actual behavior

Photo messages produce zero entries in the session transcript. Evidence from the session log (relayed turns appear as "Remote message from Telegram (user …). Carry out the request below."):

• 你能读图片吗 ("can you read images?") — relayed and answered.
• Two photos sent right after — no relayed entries at all.
• 我发送了两张，看起来你都没收到 ("I sent two, looks like you received none") — relayed; the agent correctly replied it had received only text and no attachments.

Environment

• Command Code: CLI v1.81.0 · Desktop v0.1.52+
• OS: Windows
• Terminal: Windows Terminal
• Chat platform: Telegram (Desktop app Remote control; CLI bridge shares the same relay format)

Related

• /rc Discord bridge: thinking elapsed-status persists; mid-run /rc drops events; /rc <mode> restart silently breaks streaming #974 — other /rc relay defects (stale Thinking… status; events dropped after /rc <mode> restarts).