hermes - 💡(How to fix) Fix Telegram: images sent by user are not accessible — agent spends 30+ min failing to read them [1 pull requests]

Bug Description

When a user sends an image via Telegram to Hermes, the agent cannot read or find the image. Instead of failing fast, it spends 30+ minutes attempting various approaches before finally giving up.

Steps to Reproduce

1. Send an image to Hermes via Telegram
2. Ask the agent to analyze or describe the image
3. Observe the agent attempting tool calls repeatedly (e.g. , reading attachments, etc.)
4. After ~30 minutes of retries and no progress, it concludes it cannot access the image

Expected Behavior

• The agent should either:
  • Successfully receive and read the image immediately, OR
  • Fail fast with a clear message: "I cannot access images sent via Telegram" within seconds, not 30 minutes
• No endless retry loops on an unreachable attachment

Actual Behavior

• Agent loops for 30+ minutes trying to locate/read the image
• Wastes tokens and user time
• Eventually admits defeat without having done any useful work

Environment

• Platform: Telegram gateway
• Hermes version: current main (2026-05-09)
• Model: kimi-k2.6 (via kimi-for-coding) — but model-agnostic

Additional Context

This may be related to how Telegram photo/file messages are passed into the gateway message pipeline, or how the attachment URL/path is exposed to the agent's toolset. The agent seems to not receive any usable image reference at all, yet keeps trying.