NanoClaw Channels

Pattern: Pair one channel during install; add others via project’s channel-skill flows (often Claude Code assisted). Prefer allowlists/pairing forever.

Surfaces commonly listed

WhatsApp, Telegram, Slack, Discord, Gmail, Microsoft Teams, and local CLI—verify maturity per adapter. Channels may self-register when credentials exist.

Operator habits

One channel first; separate bots for personal vs work
Never put vault secrets in chat
Mount only channel-needed workspaces into that agent
Scheduled jobs that send outbound messages count as production

vs OpenClaw channels

OpenClaw’s channel docs live under our Channels hub. NanoClaw skills/adapters are not ClawHub drop-ins—rebuild critical flows after migration.

This column

Project hub
What is it?
Install
Isolation & OneCLI
Channels
Security
Use cases
FAQ
vs OpenClaw
All OpenClaw-family alternatives

Last updated: 2026-07-14 · Independent analysis on OpenClaw Roadmap. Verify features on each project’s official site/repo—this space moves fast.