OpenClaw on WhatsApp
Link OpenClaw to your own WhatsApp number by hand and test it in your Message yourself chat.
This page links OpenClaw, running on a computer, to your WhatsApp account. It follows OpenClaw setup. To message Cue from WhatsApp without OpenClaw, use WhatsApp, which connects through Cue CLI.
These steps are manual and have not been checked end to end on Cue OS. On current Cue computers, openclaw channels list --all shows WhatsApp as not installed, so this setup will not work there until the WhatsApp plugin is added. Adding it was not tested. Cue also already runs the OpenClaw gateway on port 18789 on those computers, so the start commands below use --force to replace it.
OpenClaw's WhatsApp channel works as a linked device, the same way WhatsApp Web does. The gateway holds the WhatsApp session, and replies come from your own number.
1. Choose the setup
To test on your own number:
allowFromlists your own phone number.selfChatModeistrue.dmPolicyis"allowlist".groupPolicyis"disabled"for the first test.
Pairing, used on the Telegram and Discord pages, is not the best first setup for your own WhatsApp number.
2. Add the WhatsApp settings
Run these in this order. OpenClaw checks dmPolicy="allowlist" as soon as you set it, so allowFrom must come first.
openclaw config set channels.whatsapp.allowFrom '["+15551234567"]' --strict-json
openclaw config set channels.whatsapp.selfChatMode true --json
openclaw config set channels.whatsapp.dmPolicy '"allowlist"' --json
openclaw config set channels.whatsapp.groupPolicy '"disabled"' --jsonReplace +15551234567 with the phone number you will link.
Do not set channels.whatsapp.streaming. OpenClaw rejects that key for WhatsApp.
3. Link WhatsApp
Run:
openclaw channels login --channel whatsappThen on your phone:
- Open WhatsApp.
- Go to Settings, then Linked Devices.
- Tap Link a Device.
- Scan the QR code shown in the computer's terminal.
If the terminal prints Linked after restart; web session ready., that is normal.
4. Start the gateway
Run the gateway in the foreground and leave that terminal open:
openclaw gateway --forceOr run it in the background so you keep your prompt. Logs go to ~/.openclaw/logs/gateway-sandbox.log:
mkdir -p ~/.openclaw/logs
nohup openclaw gateway --force > ~/.openclaw/logs/gateway-sandbox.log 2>&1 &
sleep 4Check it:
openclaw channels status
tail -n 60 ~/.openclaw/logs/gateway-sandbox.logWhat you want to see:
- WhatsApp shows as linked
- a log line saying the WhatsApp web session is ready
5. Test in Message yourself
- In WhatsApp on your phone, open Message yourself.
- Send
hello.
There is no pairing step in this mode. To watch what happens, run this in a second terminal, or in the same one if the gateway runs in the background:
openclaw logs --followTroubleshooting
dmPolicy="allowlist" requires ... allowFrom. SetallowFromfirst, thenselfChatMode, thendmPolicy.channels.whatsapp: Unrecognized key: "streaming". Remove that key.- The QR login worked but no replies arrive. Check that
openclaw gatewayis still running, and runopenclaw channels status. - Cue's own WhatsApp connection uses the same number. Unlink it first, so OpenClaw is the only one listening on that number. See WhatsApp.
openclaw gateway restartsays the service is disabled. That is expected on a computer without a background service manager. Start it withopenclaw gateway --forceinstead.
WhatsApp access and model access are separate. If WhatsApp links but the assistant does not answer, finish Model auth.
Next: Model auth.