openclaw - 💡(How to fix) Fix Personal WhatsApp dmPolicy default ("pairing") leaks pair codes to every contact [1 comments, 2 participants]

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…
GitHub stats
openclaw/openclaw#75569Fetched 2026-05-02 05:33:06
View on GitHub
Comments
1
Participants
2
Timeline
1
Reactions
2
Timeline (top)
commented ×1

When OpenClaw is connected to a personal WhatsApp account (using the user's own phone number rather than a dedicated bot account), the default channels.whatsapp.dmPolicy: "pairing" causes the gateway to auto-respond to every unknown sender — i.e. every personal contact who is not on allowFrom — with a pair-code message, sent from the user's own WhatsApp number.

Root Cause

When OpenClaw is connected to a personal WhatsApp account (using the user's own phone number rather than a dedicated bot account), the default channels.whatsapp.dmPolicy: "pairing" causes the gateway to auto-respond to every unknown sender — i.e. every personal contact who is not on allowFrom — with a pair-code message, sent from the user's own WhatsApp number.

Fix Action

Workaround

Manually set: ```bash openclaw config set channels.whatsapp.dmPolicy allowlist openclaw config set channels.whatsapp.allowFrom '["+<your number>"]' --strict-json openclaw gateway restart ```

Code Example

OpenClaw: access not configured.
   Your WhatsApp phone number: +<their number>
   Pairing code: <CODE>
   Ask the bot owner to approve with: openclaw pairing approve whatsapp <CODE>
RAW_BUFFERClick to expand / collapse

Summary

When OpenClaw is connected to a personal WhatsApp account (using the user's own phone number rather than a dedicated bot account), the default channels.whatsapp.dmPolicy: "pairing" causes the gateway to auto-respond to every unknown sender — i.e. every personal contact who is not on allowFrom — with a pair-code message, sent from the user's own WhatsApp number.

Reproduction

  1. Set up OpenClaw with the personal WhatsApp channel (default config).
  2. Have any contact (not on allowFrom) send a message to your number — even a single emoji like 👍.
  3. OpenClaw replies from your account with:
    OpenClaw: access not configured.
    Your WhatsApp phone number: +<their number>
    Pairing code: <CODE>
    Ask the bot owner to approve with: openclaw pairing approve whatsapp <CODE>

Why this is a problem on personal WhatsApp

  • Every existing contact who messages you = "unknown sender" → triggers an auto-reply they never asked for.
  • Random/scam contacts (e.g. WhatsApp Business spam) also get a pair code — looks indistinguishable from a real social-engineering exchange and is confusing for the owner who sees it later in their chat.
  • The pair code itself can't be used without owner approval, but the leaked phone number + pair-instruction text creates believable phishing material.
  • It's invisible by default to the owner: replies are sent silently from their own account.

Suggested fix

For personal WhatsApp accounts (i.e. the channel is bound to the owner's own number, detectable via the connection identity), default dmPolicy to allowlist with allowFrom pre-populated to the owner's own number. Keep pairing as the default for dedicated bot accounts / business numbers where the multi-user pairing flow makes sense.

Alternatively, prompt the user during openclaw setup to choose between the two intents ("personal account — only me" vs. "shared bot — others can pair").

Workaround

Manually set: ```bash openclaw config set channels.whatsapp.dmPolicy allowlist openclaw config set channels.whatsapp.allowFrom '["+<your number>"]' --strict-json openclaw gateway restart ```

Version

  • OpenClaw 2026.4.25 (aa36ee6) on macOS 26.4.1

extent analysis

TL;DR

Manually setting dmPolicy to allowlist and configuring allowFrom with the owner's number can prevent auto-replies to unknown senders on personal WhatsApp accounts.

Guidance

  • To fix the issue, update the dmPolicy to allowlist and set allowFrom to the owner's phone number using the provided workaround commands.
  • Verify the fix by having an unknown contact send a message to the WhatsApp number and checking if an auto-reply is sent.
  • Consider setting up a dedicated bot account for OpenClaw to avoid this issue altogether.
  • Be cautious when using the pairing policy on personal WhatsApp accounts, as it can lead to unintended auto-replies and potential security risks.

Example

openclaw config set channels.whatsapp.dmPolicy allowlist
openclaw config set channels.whatsapp.allowFrom '["+1234567890"]' --strict-json
openclaw gateway restart

Replace +1234567890 with the owner's actual phone number.

Notes

This workaround is specific to OpenClaw version 2026.4.25 and may not apply to other versions. It's recommended to wait for an official fix or update to a version that defaults to allowlist for personal WhatsApp accounts.

Recommendation

Apply the workaround by manually setting dmPolicy to allowlist and configuring allowFrom with the owner's number, as this provides a temporary solution to prevent auto-replies to unknown senders on personal WhatsApp accounts.

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 Personal WhatsApp dmPolicy default ("pairing") leaks pair codes to every contact [1 comments, 2 participants]