Sending Premium Custom Emoji via OpenClaw (Telegram Plugin) π
Hi everyone! 
I'm running OpenClaw with the official Telegram plugin. I want my agent to be able to send Premium Custom Emoji (e.g., via <tg-emoji> tags or MarkdownV2).
The bot owner's account has Telegram Premium. According to the Bot API docs, bots can send Custom Emoji by passing entities or using HTML/MarkdownV2 with a valid custom_emoji_id.
However, when I try message.send:
1. HTML <tg-emoji ...> arrives as plain text (tags are escaped).
2. Markdown ... also arrives as raw text.
It seems message.send defaults to plain text or escapes markup by default.
Question:
Is there a way to force OpenClaw to use parse_mode: 'HTML' or pass raw entities? Do I need to patch the gateway config or build a custom skill for this? Any examples of a working config or payload would be awesome!
Thanks!
I'm running OpenClaw with the official Telegram plugin. I want my agent to be able to send Premium Custom Emoji (e.g., via <tg-emoji> tags or MarkdownV2).
The bot owner's account has Telegram Premium. According to the Bot API docs, bots can send Custom Emoji by passing entities or using HTML/MarkdownV2 with a valid custom_emoji_id.
However, when I try message.send:
1. HTML <tg-emoji ...> arrives as plain text (tags are escaped).
2. Markdown ... also arrives as raw text.
It seems message.send defaults to plain text or escapes markup by default.
Question:
Is there a way to force OpenClaw to use parse_mode: 'HTML' or pass raw entities? Do I need to patch the gateway config or build a custom skill for this? Any examples of a working config or payload would be awesome!
Thanks!
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
83,815Members
Resources
Similar Threads
Was this page helpful?
