> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.nvidia.com/nemoclaw/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.nvidia.com/nemoclaw/_mcp/server.

# Set Up WhatsApp

> Pair experimental WhatsApp inside an OpenClaw or Hermes sandbox and understand its durable session state.

WhatsApp support is experimental and pairs inside the sandbox rather than through a host-side token or OpenShell credential provider.

## Pair the Sandbox

Enable the channel during onboarding or with `channels add whatsapp`, rebuild the sandbox, then connect to it.
Run the agent-specific pairing command to render the QR code:

```bash
hermes whatsapp
```

## Protect Paired Session State

The sandbox stores mutable session credentials in durable `platforms/whatsapp` state.
The credentials survive rebuilds without re-pairing.
This is the runtime tradeoff of enabling WhatsApp without a host bridge: a paired sandbox can use that WhatsApp account until you unpair it or clear the durable state.

NemoClaw cannot detect cross-sandbox WhatsApp conflicts the way it does for token-based channels.
Pair only one sandbox per WhatsApp account at a time.

For non-interactive onboarding, set `WHATSAPP_ALLOWED_IDS` to a nonempty comma-separated sender list to select WhatsApp for either agent.
Hermes also uses these values as its WhatsApp sender allowlist.

Continue with [Enable Channels During Onboarding](enable-channels-during-onboarding) or [Add Channels After Onboarding](add-channels-after-onboarding).