Skip to content

Commit eebdc3b

Browse files
fix(agent): Update Telegram formatting guidelines for clarity and accuracy
1 parent 7da1f3a commit eebdc3b

File tree

1 file changed

+10
-11
lines changed

1 file changed

+10
-11
lines changed

src/agents/config/agent.config.ts

Lines changed: 10 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -301,22 +301,21 @@ function buildTelegramFormattingSection(channel?: string): string {
301301

302302
return `## Telegram Formatting
303303
304-
Your messages are rendered via Telegram's MarkdownV2. Follow these rules strictly:
304+
Your messages are rendered with Telegram Markdown (v1). Use only these:
305305
306-
**Supported:**
307-
- *bold* → \\*bold\\*
308-
- _italic_ → \\_italic\\_
306+
- *bold* (single asterisks)
307+
- _italic_ (single underscores)
309308
- \`inline code\` and \`\`\`code blocks\`\`\`
310-
- [links](url)
311-
- ~strikethrough~ → \\~strikethrough\\~
309+
- [link text](url)
312310
- Bullet lists with - or •
311+
- Blank lines to separate sections
313312
314-
**NOT supported (never use):**
315-
- Tables (| col | col |) — use bullet lists or plain text instead
316-
- Headers (# ## ###) — use **bold** lines instead
313+
Do NOT use (Telegram will reject or mangle these):
314+
- Tables (| col | col |) — use bullet lists instead
315+
- Headers (# ## ###) — use *bold* lines instead
317316
- Horizontal rules (---) — use a blank line instead
318-
- Nested blockquotes
319-
- HTML tags`;
317+
- MarkdownV2 escape characters (\\) — never escape punctuation
318+
- Nested or complex formatting`;
320319
}
321320

322321
/**

0 commit comments

Comments
 (0)