#Bug: openclaw message send --media fails with "No active WhatsApp Web listener"

1 messages · Page 1 of 1 (latest)

haughty lion
#

Bug: ⁠ openclaw message send --media ⁠ fails with "No active WhatsApp Web listener" despite WhatsApp being connected

OpenClaw version: 2026.3.13 (61d171a)
OS: Linux 6.8.0-106-generic, Node 22.22.1

Symptom:
Sending media via CLI fails immediately, even though WhatsApp is fully linked and connected. Text replies from the agent work fine (including reactions).

Command:

openclaw message send --channel whatsapp --target +49xxx
--message "..." --media /path/to/image.png

Error:

GatewayClientRequestError: No active WhatsApp Web listener (account: default).
Start the gateway, then link WhatsApp with:
openclaw channels login --channel whatsapp --account default.

⁠ openclaw channels status ⁠ output:

WhatsApp default: enabled, configured, linked, running, connected, dm:allowlist

Steps to reproduce:
1.⁠ ⁠Gateway running via systemd, WhatsApp linked & connected
2.⁠ ⁠Run the above ⁠ message send --media ⁠ command
3.⁠ ⁠Error appears instantly

What I tried:
•⁠ ⁠Gateway restart
•⁠ ⁠⁠ openclaw channels login --channel whatsapp ⁠ (returns "Linked!" immediately, no QR needed)
•⁠ ⁠Both with and without ⁠ OPENCLAW_GATEWAY_TOKEN ⁠

Note: Text-only sends from the agent session work perfectly. Only the CLI media send path seems unable to find the internal listener.