If Hermes Agent fails to send a Markdown file, check the gateway version first instead of immediately reconfiguring the messaging platform. v0.15.1 fixed Markdown file delivery issues: the previous media validation rules were too narrow and might block normal Markdown attachments. After the upgrade, it switched to a more stable rejection list logic.
First, check if the file type is blocked
If you can send regular text messages and images, but Markdown reports, summary files, or task results don't reach the chat platform, then file delivery verification is prioritized. It's different from bot token errors: token errors usually mean all messages fail; Here, it's just a certain type of attachment failure.
It is recommended to handle them in this order
- Run a version check to confirm that the Hermes Agent is lower than v0.15.1.
- After the upgrade, restart the gateway to take effect under the new media delivery rules.
- Send a very small Markdown test file, eliminating file size restrictions.
- If that still fails, check attachment permissions on platforms like Telegram, Slack, Discord, etc.
Don't delete the configuration right away. Most of the time, Markdown files fail to be sent out, not because the project files are corrupted, but because the gateway or platform permissions have not been granted.
How to determine platform restrictions
If all attachments fail, check the platform's upload permissions and network; If only large files fail, check the size limit; If only Markdown fails, prioritize checking the Hermes Agent version and gateway logs. This sequence can quickly pinpoint the problem.
