Hermes Agent Ships Telegram Rich Messages - Native Markdown Rendering Turns Telegram Into a Lightweight Dashboard
Teknium shipped Telegram Rich Messages support for Hermes Agent on June 13. Hermes output on Telegram now renders with native markdown formatting, inline links, image attachments, and PDF delivery - instead of escaping to plain text.
The feature drops the friction between agent output and readability. Cron reports, monitoring alerts, X article summaries, and research digests all land in Telegram with formatting intact.
The announcement pulled 56 likes and 7 bookmarks in the first few hours - modest numbers that reflect a utility feature, not a headliner release. The significance is in what it changes about daily workflows.
What Rich Messages Enables
Before Rich Messages, Hermes output on Telegram was plain text. Markdown characters rendered literally - asterisks around bold text, brackets on links, backticks on code. The agent could produce formatted output, but Telegram displayed it raw.
Rich Messages converts the output pipeline. Agent responses now render with:
- Bold and italic text
- Clickable inline links
- Formatted code blocks
- Image and PDF attachments
- Structured message layouts
Japanese user @sora_biz summarized the practical impact: "Hermes Agent → Telegram output with rich messages becomes very easy to read. News summaries, X article explanations, monitoring notifications, research reports, images/PDF attachments - Telegram becomes a lightweight dashboard as-is."
The "lightweight dashboard" framing captures the shift. Hermes cron jobs that previously dumped plain text into Telegram now deliver structured reports. A coverage tracker report lands with bolded headlines and clickable source links. A server monitoring alert arrives with a code block showing the error log. The agent output doesn't change - the delivery layer does.
Broader Context: Hermes on Multi-Platform
Hermes Agent already supported Telegram, Discord, and web chat as output channels. But the experience between platforms was uneven. Discord had rich embeds for some content types; Telegram was plain text. Rich Messages closes that gap.
@graanit2 posted today about deploying Hermes on a personal VPS, highlighting the multi-platform reach: "It runs on any LLM provider - DeepSeek, OpenRouter, Claude, local models. It has persistent memory, scheduled tasks, multi-platform chat (Telegram, Discord...)". The Telegram channel is a core part of that deployment story.
Separately, xProof - a cryptographic verification tool for agent outputs - was recently listed in the Hermes Skills Hub, installable with hermes skills install. The timing is notable: as agent output becomes more readable and actionable through Rich Messages, the need to verify what the agent produces becomes more acute. More trust in formatted output means more reason to prove it hasn't been tampered with.
What's Not Here
Rich Messages is a delivery-layer improvement. It does not change how cron jobs run, how skills execute, or how the agent reasons. It makes the output readable. For users running Hermes through Telegram as their primary interface, that matters.
The feature is live now. Hermes Agent users on Telegram get formatted output on the current release - no configuration required beyond having Telegram set up as a provider.
[^1]: Teknium. "Telegram has Rich Messages support now!" X. June 13, 2026. [^2]: sora_biz. "Hermes Agent → Telegram Rich Messages commentary." X. June 13, 2026. [^3]: graanit2. "I deployed Hermes Agent on my own VPS." X. June 13, 2026.