openclaw - 💡(How to fix) Fix [Bug] Image sent twice via weixin plugin - duplicate sendImageMessageWeixin calls for same mediaUrl [1 participants]

Bug Description

When replying with a MEDIA:/path/to/image.png directive in the weixin plugin, the image is sent twice to the recipient. Both images are identical (same file size: 15828 bytes) but have different file keys, indicating two separate upload+send operations.

Steps to Reproduce

1. Use agent-browser to take a screenshot
2. Output MEDIA:/tmp/screenshot.png as a reply
3. Observe that wechat receives two identical images

Expected Behavior

Image should be sent exactly once.

Actual Behavior

Log shows two separate sendImageMessageWeixin calls at the same millisecond, with different filekey values but identical fileSize:

19:10:13.227  outbound: mediaUrl=present
19:10:13.640  sendImageMessageWeixin: filekey=74546e9d2a9dacb0b08f73007d3a5fc9 fileSize=15828 (attempt 1)
19:10:13.902  outbound: mediaUrl=present (same contextToken, different temp file)
19:10:14.254  sendImageMessageWeixin: filekey=cfe2803775b65b1c4df0c14a7b245739 fileSize=15828 (attempt 2)

Both images arrive in wechat as identical 15KB files.

Root Cause Analysis

Two concurrent code paths both process the same mediaUrl:

1. sendFinalPayload (final reply path) → normalizeReplyMediaPayload → uploads
2. onToolResult callback (tool result path) → normalizeReplyMediaPayload → uploads

These appear to run concurrently in dispatchReplyFromConfig, each calling normalizeReplyMediaPayload which creates a separate temp file copy, resulting in two separate uploads.

Environment

• OpenClaw version: latest
• Plugin: openclaw-weixin (latest)
• Channel: weixin (direct chat)

Plugin Version

N/A - issue appears to be in core dispatch logic, not plugin-specific code.

Suggested Fix

Deduplicate media payloads before sending, or ensure normalizeReplyMediaPayload is called only once per unique mediaUrl in a single reply cycle.