Run OpenClaw on WhatsApp with a private-hosting path.
The official OpenClaw WhatsApp channel is QR-based and built on WhatsApp Web. That gives you a real phone-native surface, but it also means the Gateway needs a stable home if you want the assistant reachable all day.
What the current docs make clear
The safest way to explain this setup is to stay close to the official architecture and not pretend the channel is simpler than it really is.
OpenClaw documents WhatsApp as a WhatsApp Web-based channel using Baileys.
The official flow supports install-on-demand, QR login, pairing, and account-specific auth directories.
OpenClaw recommends a separate WhatsApp number when possible for cleaner routing and safety boundaries.
GetClaw helps when you want the Gateway, channel auth, and hosted workspace online without self-operating the server.
The setup decisions that matter most
Most failed WhatsApp deployments are not about AI. They are about channel policy, auth lifetime, and where the Gateway is running.
Start conservative
Use allowlists or pairing first. Do not run an open-to-the-world personal assistant on your everyday machine without access controls.
Keep the channel identity clean
A dedicated number is operationally cleaner than mixing the assistant into your main personal number too early.
Expect troubleshooting work
QR login, reconnect loops, and gateway health checks are real operational tasks when you self-host.
Host when availability matters
If the agent needs to stay reachable from your pocket all day, a hosted runtime is usually the more honest answer than a laptop-only setup.