NanoClaw

NanoClaw came out of a refusal. Its author would not hand complex software he did not understand full access to his life, so each agent here runs in its own Linux container and sees only what you explicitly mount, rather than sitting behind application-level allowlists in one shared process.

A single Node host acts as the router. A message arrives from a channel, gets written to a per-session SQLite file, and wakes the container; the agent writes back to a second SQLite file that the host polls and delivers. Two files per session with exactly one writer each removes any need for IPC or stdin piping.

The project takes a firm line on how it grows.

• Skills over features: channel adapters and alternative model providers live on separate branches, copied into your fork on demand.
• No configuration files: you change behavior by asking Claude Code to edit the code, which is small enough to review.
• Multi-channel: WhatsApp, Telegram, Discord, Slack, Teams, iMessage, Matrix, Google Chat, Webex, Linear, GitHub and email are all installable.
• Agent templates: a reusable bundle of instructions, tools and skills stamps out a ready-to-run agent carrying no secrets.
• Nothing phones home: only anonymous setup diagnostics leave the machine, and one environment variable turns those off.

One shell script installs Node, pnpm and Docker if missing, registers your credential, builds the agent container and pairs your first channel. It needs macOS or Linux, Windows through WSL2, Node 22 and Docker.