Back to updates
New releaseAug 1, 2026

nanoclaw v2.1.54

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

Share

NanoClaw

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  •   中文  •   日本語  •   한국어  •   Discord  •   repo tokens


NEW! Agents in Slack: one app per agent

With a free NanoClaw account, 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.

Quick Start


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 host process and no microservices of its own. Agents run in their own Linux containers with filesystem isolation, not merely behind permission checks.

Quick Start

[!TIP] Unsure whether you're ready to install? Paste this prompt into your coding agent on the computer where you'll run NanoClaw.

I want to install NanoClaw, a self-hosted assistant that runs agents in containers and connects them to messaging apps. The official repository is https://github.com/nanocoai/nanoclaw. Check whether this computer is ready to run its setup script, nanoclaw.sh. Use read-only checks.

Read the requirements for my checkout, or use https://docs.nanoclaw.dev/installation if I haven't cloned it yet. Check the OS (including WSL2 on Windows), Git, Bash, Node.js, pnpm, and jq. Check whether Docker is installed and whether my user can reach its daemon.

Tell me whether I'm ready to run setup, what the installer will handle, and what I need to fix first. Give the smallest next step for each blocker. Flag anything you couldn't verify.
git clone https://github.com/nanocoai/nanoclaw.git
cd nanoclaw
bash nanoclaw.sh

nanoclaw.sh walks you from a fresh machine to a named agent you can message. It:

  • installs or updates Node and pnpm, and installs Docker if missing
  • installs a credential gateway and offers to register your model credential with it when your runtime needs one (Claude by default, or Codex, Cursor or OpenCode if you pick one)
  • fetches a prebuilt agent image or builds one locally
  • pairs your first channel (Slack, Mattermost, Microsoft Teams, Telegram, Discord, WhatsApp, Dial, Signal, iMessage, or chat from the terminal)

If a wizard step fails, setup can hand it to Claude Code (or to Codex or OpenCode, if you picked one of those) to diagnose, then retry from where it broke.

Migrating from NanoClaw v1?

Run it from a fresh v2 checkout. Clone v2 into a separate parent folder (your v1 checkout is likely ~/nanoclaw) and point the script at it:

mkdir -p ~/v2 && cd ~/v2
git clone https://github.com/nanocoai/nanoclaw.git
cd nanoclaw
NANOCLAW_V1_PATH=~/nanoclaw 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, if it is installed, to finish the parts that need judgment (owner seeding, shared-memory migration, fork-customisation replay).

Run the script directly, not from inside a coding agent 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 + active scheduled tasks (it skips paused tasks, and tasks it cannot match to a migrated chat or whose schedule it cannot convert), installs the GitHub adapter if you select GitHub, 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 or pulls the agent container.

What it doesn't: switch services without asking. If your v1 service is running, it asks whether to "switch to v2" and lets you revert. Once you keep v2, or if v1 wasn't running, it stops the v1 service and keeps its unit file or plist for rollback. On Linux it is also disabled; on macOS the plist can load it again at the next login. Your v1 files are only read.

See docs/v1-to-v2-changes.md for what's different and docs/migration-dev.md for development notes.

Philosophy

Small enough to understand. One host process and no microservices of its own. If you want to understand the full NanoClaw codebase, just ask your coding agent (Claude Code, Codex, …) to walk you through it.

Secure by isolation. Agents run in Linux containers and they can only see what's explicitly mounted. Bash access is safe because commands run inside the container, not on your host.

Built for the individual user. NanoClaw isn't a monolithic framework; it's software that fits each user's exact needs. Instead of becoming bloatware, NanoClaw is designed to be bespoke. You make your own fork and have your coding agent modify it to match your needs.

Customization = code changes. No configuration sprawl. Want different behavior? Modify the code. The codebase is small enough that it's safe to make changes.

AI-native, hybrid by design. The install and onboarding flow is an optimized scripted path, fast and deterministic. When a step needs judgment, whether a failed install, a guided decision, or a customization, control passes to a coding agent: setup can hand a failed step to Claude Code, Codex or OpenCode, and your coding agent runs the customization skills. Beyond setup, core ships no monitoring dashboard or debugging UI either (optional skills such as /add-dashboard add one): describe the problem to your coding agent and it handles it.

Categories