discord-rich-message

Topics in the source

• Discord Rich Message (Components V2)
• Platform scope — HARD BOUNDARY
• Why this exists
• Discord's limits (the constraints the sender must enforce)
• The sender contract
• Resolving a channel id
• Usage shapes
• Components V2 payload shape (reference)

Discord ONLY. Components V2 (flags: 32768) is a Discord-private message protocol. It does not exist on other platforms. ❌ Feishu (飞书) → has its own interactive card / markdown-module system. Use that, never this. ❌ Slack → Block Kit. ❌ Telegram → its own entities/HTML. ❌ Email → real HTML/Markdown. ✅ Only emit this payload when the target is a Discord channel id. If a task spans multiple platforms, render Discord with this skill and render each other platform with its own native mechanism. Never copy the V2 payload across platforms. Discord's plain message body renders only a subset of Markdown. It does not render: tables (| a | b |) → shows raw pipes horizontal rules --- inline links text (anti-phishing; intentional, won't change) ####+ headings, deep nested lists So for any structured / tabular output to Discord, do NOT send a Markdown table. Send a Components V2 message (verified to render cleanly, including an accent bar + divider + monospace aligned table), or attach a file when the content outgrows the text budget. | Constraint | Value | Consequence | |---|---|---| | Plain message content | 2000 characters | Split or switch to Components V2 | | Combined text across V2 compone

This is an excerpt. Refer to the complete source and its current requirements.