openclaw - 💡(How to fix) Fix [Bug]: WhatsApp outbound media sends falsely succeed on 2026.4.5, attachment is dropped and only caption/text is delivered [4 comments, 4 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#61726Fetched 2026-04-08 02:55:21
View on GitHub
Comments
4
Participants
4
Timeline
6
Reactions
0
Author
Timeline (top)
commented ×4labeled ×2

On OpenClaw 2026.4.5, outbound WhatsApp media sends can return a successful tool result with a real-looking WhatsApp messageId, but the recipient only receives the caption/text. The actual attachment never arrives.

This affects direct message tool sends on WhatsApp.

Root Cause

But this issue seems broader, because it is happening on 2026.4.5 and appears to affect direct message tool sends too, not just MEDIA: token agent replies.

RAW_BUFFERClick to expand / collapse

Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

Summary

On OpenClaw 2026.4.5, outbound WhatsApp media sends can return a successful tool result with a real-looking WhatsApp messageId, but the recipient only receives the caption/text. The actual attachment never arrives.

This affects direct message tool sends on WhatsApp.

Environment

  • OpenClaw: 2026.4.5
  • OS: macOS (Apple Silicon)
  • Channel: WhatsApp Web / Baileys
  • Gateway mode: local LaunchAgent
  • WhatsApp account: linked and healthy
  • Text-only WhatsApp sends still work

What I tested

I tested outbound WhatsApp sends using the message tool with:

  1. an image
  2. a normal audio file
  3. an audio send with asVoice=true

All 3 returned successful results with:

  • channel: "whatsapp"
  • via: "gateway"
  • mediaUrl: <local file path>
  • a runId
  • a WhatsApp messageId
  • a toJid

Example behavior:

  • tool returns success
  • gateway logs show message sent
  • recipient only gets the caption/text like:
    • whatsapp image test from lana
    • whatsapp audio file test from lana
    • whatsapp voice-note test from lana
  • no actual attachment appears in WhatsApp

Expected behavior

If media is provided, WhatsApp should deliver the actual attachment plus optional caption.

Actual behavior

The send is reported as successful, but only the text/caption is delivered. The media payload is silently dropped.

Important details

  • This is not a total WhatsApp outage.
  • Text-only sends still work.
  • This is not just a FishAudio or voice-note generation problem.
  • This is not just the PTT lane.
  • Image sends, plain audio sends, and asVoice=true sends can all degrade into text-only delivery.
  • WhatsApp remains linked and healthy in openclaw status --deep.

Investigation so far

I diffed the npm tarballs for 2026.4.2 and 2026.4.5.

Findings:

  • The low-level WhatsApp/Baileys payload builder appears basically unchanged between those versions.
  • The existing audio -> ptt: true behavior was already present before 2026.4.5, so that alone does not explain this regression.
  • 2026.4.5 includes significant refactoring in the higher-level WhatsApp outbound plumbing, especially around:
    • send-lXVwx8YQ.js
    • attached channel result adapters
    • outbound send dependency wiring
    • WhatsApp channel setup/runtime packaging

Current suspicion:

  • the regression is likely in the higher-level outbound media mapping or delivery path before the final WhatsApp socket send
  • the runtime appears to falsely acknowledge success while the attachment is lost and only the caption survives

Related issue

This looks related in spirit to:

  • #54131

But this issue seems broader, because it is happening on 2026.4.5 and appears to affect direct message tool sends too, not just MEDIA: token agent replies.

Repro idea

Using message tool or equivalent CLI send:

  • send image with caption on WhatsApp
  • send audio file on WhatsApp
  • send audio with asVoice=true

Observe:

  • success result with messageId
  • recipient receives caption text only
  • no media attachment

Steps to reproduce

  1. Install or update OpenClaw to 2026.4.5.
  2. Make sure WhatsApp is linked and shows healthy in openclaw status --deep.
  3. Send a WhatsApp message with the message tool using a local image file and a caption.
  4. Observe the tool result:
    • it returns success
    • includes channel: "whatsapp"
    • includes via: "gateway"
    • includes a real-looking messageId
  5. Check the recipient phone.
  6. Notice that only the caption text arrives, and the image attachment is missing.

Also reproduces with audio

Repeat the same test with:

  • a normal audio file
  • an audio file with asVoice=true

Observed result is the same:

  • tool reports success
  • WhatsApp recipient receives only the caption/text
  • no media attachment is delivered

Expected behavior

In previous version, media attachment (audio, image, etc) would successfully send to Whatsapp.

Actual behavior

Caption text received via Whatsapp without the actual attachment.

OpenClaw version

2026.4.5

Operating system

macOS 26.4

Install method

npm

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> gpt-5.4

Additional provider/model setup details

No response

Logs, screenshots, and evidence

Impact and severity

No response

Additional information

No response

extent analysis

TL;DR

The issue can likely be fixed by investigating and correcting the higher-level WhatsApp outbound media mapping or delivery path in the OpenClaw 2026.4.5 version.

Guidance

  • Review the changes made in the 2026.4.5 version, specifically in the files send-lXVwx8YQ.js and the attached channel result adapters, to identify potential issues with media attachment handling.
  • Verify that the media files are being properly uploaded and processed before being sent to WhatsApp.
  • Test the message tool with different types of media attachments (e.g., images, audio files) to see if the issue is specific to certain file types.
  • Compare the behavior of the 2026.4.5 version with previous versions (e.g., 2026.4.2) to identify any changes that may have introduced the regression.

Example

No specific code example is provided, as the issue is related to a complex system and requires a deeper investigation of the OpenClaw codebase.

Notes

The issue seems to be related to the higher-level outbound media mapping or delivery path, and not with the low-level WhatsApp/Baileys payload builder. The fact that text-only sends still work suggests that the issue is specific to media attachments.

Recommendation

Apply a workaround by downgrading to a previous version of OpenClaw (e.g., 2026.4.2) until the issue is fixed in a future release. This is because the issue is likely related to changes made in the 2026.4.5 version, and downgrading may provide a temporary solution.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

In previous version, media attachment (audio, image, etc) would successfully send to Whatsapp.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING