Summary

On Hermes Agent v0.10.0, Telegram text messages are delivered successfully, but file attachments are not actually delivered, even though Hermes reports success and returns a Telegram message ID.

Environment

• Hermes Agent: v0.10.0
• Platform: Telegram direct message
• Profile: research
• Gateway: profile-level gateway running
• OS: Linux
• Model/provider config is valid, text chat works normally

Observed behavior

Works

• Sending plain text messages to Telegram works correctly

Fails

• Sending file attachments does not reach Telegram
• Hermes still reports success, for example:
  • chat_id: 2027843809
  • message ID: 686 for .docx
  • message ID: 691 for test.txt

But the Telegram client never receives the file.

Reproduction

1. Start Hermes with a profile that has Telegram configured and gateway running
2. Open chat:

   hermes profile use research
   hermes chat

3. Ask Hermes to send a plain text Telegram message
   Result: delivered successfully
4. Ask Hermes to create and send a small file like test.txt
   Result: Hermes reports success, Telegram receives nothing
5. Ask Hermes to send a .docx file
   Result: same, Hermes reports success, Telegram receives nothing

Expected behavior

If Hermes reports a successful Telegram file send, the file should actually appear in the Telegram chat.

Actual behavior

Hermes reports success and returns a Telegram message ID, but no file appears in Telegram.

Notes

This does not look like a basic Telegram configuration issue because:

• text delivery works
• chat_id is correct
• gateway is running
• profile config and model config are valid

It appears specific to Telegram file/document delivery or success-state reporting after attachment send.

Request

Please check:

• Telegram document/file upload path
• whether Hermes is treating a queued or partial send as a successful send
• whether the returned Telegram message ID is real / confirmed
• any attachment-specific API handling differences vs plain text