Hermes Agent adds Telegram Rich Messages support

• Teknium's product post said Hermes Agent now supports Telegram Rich Messages, giving bots a native richer rendering path instead of flattened chat output.
• The official Telegram docs page says the feature uses Telegram Bot API 10.1 rich rendering for tables, task lists, headings, nested blockquotes, footnotes, math, and anchors.
• Teknium's profile update also added --clone-from, so new Hermes profiles can start from any existing profile, not just the default one.
• The linked profiles docs show that --clone-from can copy config, skills, and SOUL from a chosen source profile, with --clone-all available for a fuller copy.

Teknium's Telegram Rich Messages post landed a few hours before Teknium's profile cloning update, which makes this a tidy two-part ship: Telegram bots got richer output, and multi-profile setups got less annoying to duplicate. The docs also bury two useful implementation details: Telegram rich rendering falls back automatically when a message is too large or rejected, and cloned profiles keep their own scoped state even when they share the same user workspace.

Hermes Agent's Telegram integration now has an opt-in rich rendering path. According to the official Telegram docs page, final replies use Telegram's native sendRichMessage, while DM streaming previews use sendRichMessageDraft so the draft matches the final formatted reply.

That richer path covers more than bold text. The docs explicitly call out tables, task lists, headings, nested blockquotes, collapsible sections, footnotes, formulas, underline, subscript, superscript, marked text, and anchors.

Later the same day, Teknium's profile update shipped a smaller but practical workflow change: new profiles can now clone from any existing profile.

The linked profiles docs show the new command:

• hermes profile create work --clone-from coder
• hermes profile create work-backup --clone-from coder --clone-all

The docs say --clone-from directly selects the source profile and implies a config, skills, and SOUL clone. --clone-all extends that into a fuller copy.

The Telegram docs add one implementation detail missing from the launch post: the rich path is skipped automatically when content exceeds Telegram's 32,768 byte rich text limit, and it also falls back to MarkdownV2 if Telegram rejects the payload for parser or endpoint reasons.

The profile docs add a similar under-the-hood detail for cloning. New profiles share the same user workspace, but each profile still builds its own observations and identity because Hermes scopes state to that profile's HERMES_HOME directory.