Why does OpenClaw send WhatsApp media replies twice?

In v2026.4.15, reply-media normalization runs through two paths for the same reply, causing duplicate outbound media files.

Which OpenClaw version has the WhatsApp duplicate media bug?

Version 2026.4.15 introduced this regression. It affects any WhatsApp request that produces a media response.

Is the OpenClaw WhatsApp duplicate media bug fixed?

As of April 25, 2026, the issue is open on GitHub (Issue #68056). No fix has been released yet.

Does the duplicate WhatsApp media affect text messages?

No, only media replies (charts, images, documents) are duplicated. Text-only responses are not affected.

How to work around OpenClaw WhatsApp media sent twice?

Set channels.whatsapp.blockStreaming: true as a temporary workaround, though this may affect other media features.

← Back to dashboard

clawsmith.com/signal/openclaw-whatsapp-media-reply-duplicate-4-15

⚠ IssueWide OpencoreLive

OpenClaw 2026.4.15 Sends Every WhatsApp Media Reply Twice

In OpenClaw v2026.4.15, every WhatsApp request that produces a single media response results in two identical media replies being sent a few hundred milliseconds apart. Root cause is reply-media normalization running through two paths for the same reply.

Product Idea from this Signal

A CLI tool that snapshots your OpenClaw state before updates, runs the upgrade in a sandboxed dry-run against your live config, and auto-rolls back if any health check fails

1667.8k ▲

OpenClaw ships updates every 2-3 days and each one risks breaking exec permissions, crashing the gateway, saturating CPU with plugin loading bugs, or silently deleting cron jobs. Four separate regressions in April 2026 alone (v2026.4.1 sandbox, v2026.4.5 CPU, v2026.4.14 memory timeouts, update command wiping Feishu and crons) hit thousands of self-hosters with no rollback path. The built-in openclaw doctor only validates config schema after the fact. This tool wraps the entire update lifecycle: snapshot state, dry-run the upgrade against your actual agent/cron/channel config, diff the before/after, and block or auto-rollback if anything regresses.

CLIOPEN-SOURCEDEVTOOLSELF-HOSTEDRELIABILITY

CompetitiveView Opportunity →