NanoClaw

Key features

• Thirteen messaging channels WhatsApp, Telegram, Discord, Slack, Microsoft Teams, iMessage, Matrix, Google Chat, Webex, Linear, GitHub, WeChat, and email via Resend connect through install-on-demand channel skills, and several can run at once.[1]

• Per-session Docker isolation Each active session gets its own Linux container on macOS, Linux, or Windows via WSL2, so shell commands run inside the sandbox and agents see only explicitly mounted folders.[1][2]

• Credential gateway Agents never hold raw API keys; outbound requests route through an installed gateway that injects credentials at request time and enforces per-agent policies and rate limits.[1][2]

• Flexible isolation modes Each channel can map to its own private agent, share one agent with unified memory but separate conversations, or fold several channels into a single shared session.[1][2]

• Per-agent workspace Every agent group keeps its own instructions file, memory, credentials, and mounts, so nothing crosses between agents unless explicitly wired.[1][2]

• Scheduled tasks Recurring jobs run on the configured provider and message results back, with optional script gates that skip waking the agent when there is no work.[1][2][3]

• Skills over features Channels and providers ship as installable skills from registry branches, so each fork contains only the integrations its owner chose.[1]

• Provider choice per agent Claude via the official Agent SDK is the default, with Codex, OpenCode-backed providers, and local Ollama models as drop-in options configurable per group.[1][2]

Who will love it

• Privacy-minded individuals gain a verifiable story for handing an agent personal conversations through the container boundary, credential gateway, and a codebase small enough to read.[1][2]

• Messaging-first users get an assistant where they already talk, including scheduled briefings delivered to their phone.[1][2]

• Tinkerers who fork benefit from the skills model and per-agent workspaces that reward trimming a fork to exactly their channels, providers, and tools.[1]

Who should avoid it

• Anyone wanting zero setup should pick a hosted assistant, since Docker, a powered-on host computer, and a separate AI account are mandatory.[1][2]

• Non-technical households face installer failures that hand off to Claude Code for diagnosis, which assumes terminal comfort.[1]

• Teams needing managed guarantees find only a community Discord, with no enterprise support plan, SSO evidence, or managed hosting observed.[1][2]

Alternatives and compatibility