Summary

In environments that require a proxy to reach api.telegram.org, the send_message tool fails to deliver any media files (photos, videos, audio, documents) because the Bot instance it creates has no proxy configured — unlike the gateway adapter which correctly uses one.

Problem

The gateway adapter (gateway/platforms/telegram.py) resolves the proxy via resolve_proxy_url("TELEGRAM_PROXY") and passes it to HTTPXRequest, so all gateway replies work fine behind a proxy.

However, the send_message tool (tools/send_message_tool.py) creates its own separate Bot instance without any proxy:

# send_message_tool.py — _send_telegram()
bot = Bot(token=token)  # direct connection to api.telegram.org — no proxy

This bot is used for both text and media sends. In proxy-dependent environments, the TCP connection to api.telegram.org cannot be established directly, causing every send_message call to timeout. The gateway itself is unaffected because it uses a different, properly proxied Bot instance.

Fix

Reuse the same proxy resolution chain as the gateway adapter:

_proxy_url = resolve_proxy_url("TELEGRAM_PROXY", target_hosts=["api.telegram.org"])
if _proxy_url:
    _req = HTTPXRequest(proxy=_proxy_url, connect_timeout=10.0, read_timeout=20.0, write_timeout=20.0)
    bot = Bot(token=token, request=_req)
else:
    bot = Bot(token=token)  # no proxy needed

Timeout values match the gateway adapter (telegram.py lines 1219–1221). When no proxy is configured, behavior is unchanged.

Testing

Verified locally with TELEGRAM_PROXY:

Related

• Telegram media delivery: albums silently degrade, captions leak into streamed text, and per-item captions aren't supported #9291 — Telegram media delivery failures
• Gateway Telegram adapter ignores HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT — large media uploads time out at PTB's 20s default #21757 — HERMES_TELEGRAM_HTTP_MEDIA_WRITE_TIMEOUT not wired to PTB