openclaw - 💡(How to fix) Fix [Bug]: WhatsApp links successfully, but peers/groups discovery is empty and the gateway reconnects repeatedly with status 499 [1 participants]

Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

After linking WhatsApp successfully in OpenClaw, the channel appears configured and connects, but WhatsApp discovery is not usable: openclaw directory peers list --channel whatsapp only returns self, openclaw directory groups list --channel whatsapp returns no groups, and the gateway repeatedly disconnects/reconnects with status 499.

Steps to reproduce

Steps to reproduce

Run OpenClaw 2026.3.28 (f9b1079) in Docker. Link WhatsApp successfully via openclaw configure and complete QR pairing. Verify the channel is configured/linked. Run:

openclaw directory peers list --channel whatsapp openclaw directory groups list --channel whatsapp Observe that peers only shows self and groups returns no groups. Observe repeated gateway events:

WhatsApp gateway disconnected (status 499) WhatsApp gateway connected

Expected behavior

After successful WhatsApp linking, OpenClaw should expose usable WhatsApp discovery information (for example recent peers and/or groups) or document a supported alternative way to discover chats/groups/JIDs, and the WhatsApp gateway should remain stable without repeated disconnect/reconnect loops.

Actual behavior

WhatsApp links successfully, but directory peers only returns self, directory groups returns no groups, and the gateway repeatedly disconnects/reconnects with status 499.

OpenClaw version

2026.3.28 (f9b1079)

Operating system

Ubuntu 24.04.4 LTS (host) / Docker container running OpenClaw

Install method

Docker (ghcr.io/hostinger/hvps-openclaw:latest)

Model

openai-codex/gpt-5.4

Provider / routing chain

Not relevant for this issue (WhatsApp channel behavior)

Additional provider/model setup details

I also inspected the installed runtime and it appears the WhatsApp implementation internally handles values such as remoteJid, groupSubject, groupParticipants, and group metadata, so it looks like the runtime may know more than the current CLI exposes.

Logs, screenshots, and evidence

Observed evidence:

WhatsApp linked successfully via QR during openclaw configure.
Status output showed WhatsApp as configured and linked.
openclaw directory peers list --channel whatsapp returned only self.
openclaw directory groups list --channel whatsapp returned No groups found.
This remained unchanged after waiting for sync and after generating activity in a non-sensitive test group.
Gateway/system events repeatedly showed:

WhatsApp gateway disconnected (status 499)
WhatsApp gateway connected
Inspecting the local WhatsApp session JSON did not reveal recent chats/groups/contact metadata.
Inspecting the installed runtime code suggests the WhatsApp runtime internally handles values such as remoteJid, groupSubject, and groupParticipants, so the runtime may know more than the current CLI exposes.

Impact and severity

Affected: OpenClaw users relying on the WhatsApp channel for operational use after successful linking Severity: Medium-High (channel links successfully but practical discovery/send workflows are blocked or significantly degraded) Frequency: Always observed for peers/groups discovery; reconnect loop observed repeatedly at roughly 1-minute intervals Consequence: Users cannot reliably discover recent contacts/groups from the CLI, cannot easily resolve chat/group targets for operational workflows, and repeated reconnects may reduce confidence in channel stability

Additional information

This is especially impactful for workflows that depend on reading recent WhatsApp group context or sending to known chats without manually recovering raw JIDs.