Summary
The WhatsApp provider logs "Listening for personal WhatsApp inbound messages" at startup. Group messages are captured by the web monitor (web-inbound module) but are not routed to agent sessions unless the group is registered in channels.whatsapp.groups.
The log message is misleading — it implies only DM messages are being listened to, but group messages ARE received by the monitor. They just aren't dispatched.
Suggestion
- Log should say "Listening for WhatsApp inbound messages (DM + N groups)" with the count of configured groups
- When a
web-inbound message arrives from an unregistered group, emit a debug/warn log: "Dropping message from unregistered group. Add to channels.whatsapp.groups to enable."
- Document clearly that
channels.whatsapp.groups is required for inbound routing, not just groupAllowFrom
Environment
- OpenClaw: 2026.5.12, 2026.5.18
Summary
The WhatsApp provider logs "Listening for personal WhatsApp inbound messages" at startup. Group messages are captured by the web monitor (
web-inboundmodule) but are not routed to agent sessions unless the group is registered inchannels.whatsapp.groups.The log message is misleading — it implies only DM messages are being listened to, but group messages ARE received by the monitor. They just aren't dispatched.
Suggestion
web-inboundmessage arrives from an unregistered group, emit a debug/warn log: "Dropping message from unregistered group. Add to channels.whatsapp.groups to enable."channels.whatsapp.groupsis required for inbound routing, not justgroupAllowFromEnvironment