nanocoai /nanoclaw
A lightweight alternative to OpenClaw that runs in containers for security. Connects to WhatsApp, Telegram, Slack, Discord, Gmail and other messaging apps,, has memory, scheduled jobs, and runs directly on Anthropic's Agents SDK
★ 31,117⑂ 12,647👁 124⑃ 3,377● 920▤ 16
+1
Daily
+40
Weekly
31,117
stars
12,647
forks
124
watchers
3,377
prs
920
issues
16
releases
README
An AI assistant that runs agents securely in their own containers. Lightweight, built to be easily understood and completely customized for your needs. nanoclaw.dev • docs • 中文 • 日本語 • 한국어 • • --- Agents in Slack: one app per agent Setup provisions each agent its own Slack app: manifest, avatar, and workspace install, no tokens to paste. Spawn teammates from chat: every one gets its own bot identity, container, and memory, with shared rooms and canvases. --- Why I Built NanoClaw OpenClaw is an impressive project, but I wouldn't have been able to sleep if I had given complex software I didn't understand full access to my life. OpenClaw has nearly half a million lines of code, 53 config files, and 70+ dependencies. Its security is at the application level (allowlists, pairing codes) rather than true OS-level isolation. Everything runs in one Node process with shared memory. NanoClaw provides that same core functionality, but in a codebase small enough to understand: one process and a handful of files. Agents run in their own Linux containers with filesystem isolation, not merely behind permission checks. Quick Start bash git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2 cd nanoclaw-v2 bash nanoclaw.sh nanoclaw.sh walks you from a fresh machine to a named agent you can message. It installs Node, pnpm, and Docker if missing, installs a credential gateway and registers your Anthropic credential with it, builds the agent container, and pairs your first channel (Slack, Telegram, Discord, WhatsApp, iMessage, or a local CLI). If a step fails, Claude Code is invoked automatically to diagnose and resume from where it broke. Migrating from NanoClaw v1? Run from a fresh v2 checkout next to your v1 install: bash git clone https://github.com/nanocoai/nanoclaw.git nanoclaw-v2 cd nanoclaw-v2 bash migrate-v2.sh migrate-v2.sh finds your v1 install (sibling directory, or NANOCLAW_V1_PATH=/path/to/nanoclaw), migrates state into the v2 checkout, then execs into Claude Code to finish the parts that need judgment (owner seeding, shared-memory migration, fork-customisation replay). Run the script directly, not from inside a Claude session — the deterministic side needs interactive prompts and real shell I/O for Node/pnpm bootstrap, Docker, the credential gateway, and the container build. What it does: merges .env, seeds the v2 DB from registered_groups, copies group folders + session data + scheduled tasks, installs the channel adapters you select, copies channel auth state (including the Baileys keystore for WhatsApp — LID mapping is now resolved per-message by the Baileys v7 adapter, not migrated), builds the agent container. What it doesn't: flip the system service. Pick "switch to v2" at the prompt, or do it manually after testing — your v1 install is left untouched. See docs/v1-to-v2-changes.md for what's different and docs/m
Top issues
#1503nanoclaw.dev has an invalid ssl cert right now19 comments · 2026-03-28#1984Provider support for custom/local OpenAI-compat endpoints (Codex + OpenCode)6 comments · 2026-04-24#3529update-nanoclaw skill refresh: local adapters fail validation or get overwritten, no opt-out5 comments · 2026-08-25#1163Use OpenCode (and its JS SDK) instead/parallel with Claude Code (and its Agents SDK)5 comments · 2026-03-16#3338Codex WebSocket idle retry is hidden until NanoClaw’s 10-minute turn timeout4 comments · 2026-08-18#2404Double delivery when agent uses send_message MCP tool and <message> blocks in the same turn4 comments · 2026-05-10#3716PreCompact conversation-archive writes an unbounded, full-rewrite file per firing — real cause of a production OOM crash loop3 comments · 2026-09-04#3096feat: Add /add-line skill for LINE Official Account channel support3 comments · 2026-07-20
Discussions
#3880How to connect Google Calendar to my claw?1 comments · 2026-09-24#3723Multiple Telegram bots for separate agent groups1 comments · 2026-09-05#2887Who's the "I" in "Why I Built NanoClaw" in the README?0 comments · 2026-06-29#2684NanoClaw event in SF on June 110 comments · 2026-06-03#2663Permission request: Agent Valve survey for AI agents/operators0 comments · 2026-05-31#2631free qwen3.7 api very fast0 comments · 2026-05-28#2616Tiny trends & Tails0 comments · 2026-05-25#2594adaptive forestry0 comments · 2026-05-23
Latest release
v2026.10.0 v2026.10.0 2026-10-09NanoClaw 2026.10.0 is the first release with calendar version numbers and the first one /update-nanoclaw installs by default: updates now follow published releases instead of the tip of main. It was tested first as 2026.10.0-rc.1 and 2026.10.0-rc.2 on the beta channel. It also makes updates and rollbacks more dependable, lets Iron Proxy reach a keyless local model over plain HTTP, routes the service through an outbound proxy when you have one, and shows Claude's own reason when a run fails. Iron Proxy installs need one setup rerun, so check the section below before you update. ⚠️ Before you