Set Up WhatsApp
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:
NemoClaw validates the gateway URL before pairing and renders the WhatsApp QR code in a compact terminal form so it fits in smaller terminal windows.
If pairing exits with a gateway close such as 1008, rerun the login command once, then check nemoclaw <sandbox> channels status --channel whatsapp to diagnose the gateway and session path separately from QR rendering.
Protect Paired Session State
The sandbox stores mutable session credentials in durable 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.
Continue with Enable Channels During Onboarding or Add Channels After Onboarding.