openclaw - 💡(How to fix) Fix [Bug] Text + MEDIA: sends as two separate Discord messages (text first, attachment second)

Description

When an assistant response contains both text content and a MEDIA: attachment, OpenClaw sends them as two separate Discord messages instead of one combined message. This creates a confusing "doubled" appearance where the text appears in one message and the file attachment in the next.

Root Cause

In block-reply-pipeline-DEYxmc4h.js, the createBlockReplyCoalescer function handles media payloads explicitly:

if (hasMedia) {
    flush({ force: true });  // ← flushes ANY buffered text FIRST as separate message
    onFlush(payload);         // ← then sends media as SEPARATE message
    return;
}

When a MEDIA payload arrives, the coalescer:

1. Flushes any buffered text as one Discord message
2. Sends the media payload as a second Discord message

Discord's API supports sending 1 file + caption text in a single API call (/channels/{id}/messages with files[] + content). The coalescer should merge the buffered text into the media payload's content field instead of flushing it separately.

Expected Behavior

Text + MEDIA: in the same assistant turn should arrive as one Discord message with the text as the message content and the file attached.

Workaround

Keeping text before MEDIA: extremely minimal (e.g., just a few characters) reduces the visual impact, but the structural split still happens.

Impact

Every assistant response that includes both text and a file attachment gets doubled on Discord. This is a recurring user pain point that cannot be fixed from prompts or configuration alone.

Environment

• OpenClaw 2026.5.7 (eeef486)
• Channel: Discord
• Platform: macOS (arm64)