Manage SandboxesMessaging Channels

Choose Messaging Channels

View as Markdown

NemoClaw supports Telegram, Discord, Slack, WeChat, WhatsApp, and Microsoft Teams for OpenClaw and Hermes sandboxes. OpenShell-managed processes and gateway resources carry channel traffic.

For token-based channels, NemoClaw registers credentials with OpenShell providers. WeChat uses a host-side QR scan during onboarding to capture a token.

WhatsApp pairs inside the sandbox through a QR scan and intentionally stores mutable session state there. Microsoft Teams uses Bot Framework credentials plus a public HTTPS webhook that forwards to the sandbox.

NemoClaw writes the selected channel configuration into the sandbox image and keeps runtime delivery under OpenShell control.

Experimental Channels

WeChat, WhatsApp, and Microsoft Teams are experimental. WeChat and WhatsApp rely on QR-based pairing flows that are more fragile than token-based bots.

Microsoft Teams requires an externally reachable webhook path that depends on your host networking setup. Interfaces, defaults, and supported features can change, and NVIDIA does not recommend these channels for production use.

Compare Channel Requirements

ChannelRequired credentials or pairingOptional settingsSetup guide
TelegramTELEGRAM_BOT_TOKENDM allowlist, group policy, mention modeSet Up Telegram
DiscordDISCORD_BOT_TOKENServer ID, user ID, mention modeSet Up Discord
SlackSLACK_BOT_TOKEN, SLACK_APP_TOKENUser and channel allowlistsSet Up Slack
WeChatHost-side QR scanDM allowlistSet Up WeChat
WhatsAppIn-sandbox QR pairingHermes sender allowlist and non-interactive channel selectionSet Up WhatsApp
Microsoft TeamsMSTEAMS_APP_ID, MSTEAMS_APP_PASSWORD, MSTEAMS_TENANT_IDUser allowlist, webhook port, mention modeSet Up Microsoft Teams

Prepare the Host and Policy

  • Use a machine where you can run nemohermes onboard.
  • Prepare the token, app credentials, or paired phone required by each selected channel.
  • Select the matching network policy preset or equivalent custom egress rules for each channel.
  • Confirm Docker is running and your user can access the Docker socket through the docker group or the documented sudo workflow.

Use host-side nemohermes <sandbox> channels commands. Do not mutate messaging configuration directly inside the sandbox because NemoClaw generates /sandbox/.hermes/.env and Hermes config at image build time, and changes inside the running container do not persist across rebuilds.

nemohermes tunnel start does not start chat bridges. It starts optional host services such as a cloudflared tunnel when that binary is present. Refer to Run Sandboxes for tunnel management.

Next Steps