openclaw - 💡(How to fix) Fix Misleading log: Listening for personal WhatsApp inbound messages — group messages received but not routed

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…

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.

Error Message

  1. 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."

Root Cause

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.

Fix Action

Fix / Workaround

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.

RAW_BUFFERClick to expand / collapse

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

  1. Log should say "Listening for WhatsApp inbound messages (DM + N groups)" with the count of configured groups
  2. 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."
  3. Document clearly that channels.whatsapp.groups is required for inbound routing, not just groupAllowFrom

Environment

  • OpenClaw: 2026.5.12, 2026.5.18

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…

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Misleading log: Listening for personal WhatsApp inbound messages — group messages received but not routed