Manage SandboxesMessaging Channels

Enable Channels During Onboarding

View as Markdown

Enable channels during onboarding when you are creating or recreating a sandbox.

Use the Interactive Picker

When the wizard reaches Messaging channels, it lists Telegram, Discord, Slack, WeChat, WhatsApp, and Microsoft Teams when the selected agent supports them. Press a channel number to toggle it on or off, then press Enter when done.

The OpenClaw picker also lists experimental Google Chat. Google Chat enrollment is interactive because you must set and confirm the public HTTP endpoint in Google Cloud Console. Refer to Set Up Google Chat before selecting it.

If you select no channels, pressing Enter skips messaging setup. If the current host inputs do not include a token-based channel token, the wizard prompts for it and stages it for the current onboarding process.

If you enable WeChat, the wizard renders a QR code, polls Tencent’s iLink gateway, and captures the bot token after you scan the QR with WeChat on your phone. The login has an eight-minute deadline, refreshes the QR up to three times on expiry, and follows iLink’s IDC redirects automatically.

Keep the terminal in the foreground until you see ✓ WeChat login confirmed.

WhatsApp uses QR pairing instead of a host-side token, so the wizard does not prompt for one. It prints pairing instructions, and you complete the pairing inside the sandbox after rebuild. NemoClaw selects the matching network policy preset during policy setup so the channel can reach its provider API.

Prepare Scripted Inputs

Export the credentials and optional settings for the channels you want to enable:

$export TELEGRAM_BOT_TOKEN="<your-bot-token>"
$export TELEGRAM_REQUIRE_MENTION=1
$export DISCORD_BOT_TOKEN="<your-discord-bot-token>"
$export DISCORD_SERVER_ID="<your-discord-server-id>"
$export SLACK_BOT_TOKEN="<your-slack-bot-token>"
$export SLACK_APP_TOKEN="<your-slack-app-token>"
$export SLACK_ALLOWED_USERS="<your-slack-member-id>"
$export SLACK_ALLOWED_CHANNELS="<your-slack-channel-id>"
$export WHATSAPP_ALLOWED_IDS="<your-whatsapp-sender-id>"
$export MSTEAMS_APP_ID="<your-teams-app-id>"
$export MSTEAMS_APP_PASSWORD="<your-teams-client-secret>"
$export MSTEAMS_TENANT_ID="<your-teams-tenant-id>"
$export TEAMS_ALLOWED_USERS="<your-entra-object-id>"
$export MSTEAMS_PORT=3978

The placeholder values are quoted because angle brackets are shell metacharacters. The quotes keep the export from triggering a redirection or syntax error when you replace the placeholder with a real value.

This release does not support non-interactive WeChat configuration because the iLink QR handshake requires a human to scan the QR on a paired phone. Run nemoclaw onboard interactively when you want to enable WeChat. For non-interactive WhatsApp selection, set WHATSAPP_ALLOWED_IDS to a nonempty comma-separated sender list.

Google Chat also requires interactive enrollment. Supported non-interactive onboarding skips it, because the Google Cloud Console endpoint and app principal steps need an operator.

Run Onboarding

$nemoclaw onboard

Complete the wizard so the blueprint can create OpenShell providers where needed, such as <sandbox>-telegram-bridge, <sandbox>-teams-bridge, or <sandbox>-wechat-bridge. NemoClaw compiles the selected channel configuration into NEMOCLAW_MESSAGING_PLAN_B64 for the sandbox image build. The build applies the selected agent configuration, writes reduced runtime metadata to /usr/local/share/nemoclaw/messaging-runtime-plan.json, and removes the full build plan from the runtime environment. Credential bindings remain OpenShell credential placeholders, so raw messaging credentials do not enter the sandbox image or agent configuration.

Remove a Channel

Use channels remove when you want to delete a channel’s OpenShell provider, runtime configuration, and matching network policy. This action can also clear stored pairing state. Use channels stop when you want to pause the channel without deleting credentials or pairing state.

$nemoclaw <sandbox> channels remove <channel>

Accept the rebuild to remove the channel configuration and its network policy preset from the replacement sandbox. When onboarding runs without a terminal on stdin or with NEMOCLAW_NON_INTERACTIVE=1, NemoClaw queues the removal. Run nemoclaw <sandbox> rebuild to apply it. Clearing the channel’s host environment variables is not a removal signal when the matching provider remains in OpenShell. Onboarding reuses that provider and keeps the channel selected, including its network egress.

For a QR-paired channel such as WhatsApp, only channels remove clears the in-sandbox pairing state. Refer to Manage Messaging Channels for channel-specific removal effects and recovery steps.

Verify the Result

After the sandbox is running, send a message to the configured bot or app. If delivery fails, inspect sandbox logs and confirm that the matching network policy preset is active. Refer to Messaging bridge appears running but no messages arrive for remediation.