NanoClaw
Your personal AI agent. Secure. Lightweight. Yours.
The official website for NanoClaw, the secure personal AI agent. NanoClaw runs securely in containers, built to be understood and customized for your own needs.
Why NanoClaw?
NanoClaw delivers the same core functionality in a codebase you can actually understand.
| OpenClaw | |
|---|---|---|
| Source files | 15 | 3,680 |
| Lines of code | ~3,900 | 434,453 |
| Dependencies | <10 | 70 |
| Config files | 0 | 53 |
| Time to understand | 8 minutes | 1–2 weeks |
| Security model | OS container isolation | Application-level checks |
| Architecture | Single process + isolated containers | Single process, shared memory |
What It Supports
Everything NanoClaw supports out of the box, and nothing you don't need.
Messaging Apps
WhatsApp, Telegram, and more. Message your NanoClaw agent from your phone through the apps you already use.
Container Isolation
Agents run in Apple Container (macOS) or Docker. They can only see what you explicitly mount.
Agent Swarms NEW
NanoClaw can spin up teams of specialized agents that collaborate on complex tasks. First personal AI to support this.
Per-Group Memory
Each group has its own CLAUDE.md memory, isolated filesystem, and runs in its own container sandbox.
Scheduled Tasks
Recurring jobs that run Claude and message you back. Morning briefings, weekly reviews, and more.
Skills System
Extend functionality without bloat. Add Gmail, Telegram, or custom capabilities via skills.
AI-Native Setup
No installation wizards. Claude Code guides everything: dependencies, auth, containers, services.
Web Access
NanoClaw can search the web, fetch content, and browse pages to research anything.
Architecture
NanoClaw is a single Node.js process. Agents in isolated containers. 15 source files.
Single Process
One Node.js process polls for messages, manages queues, spawns containers, and handles IPC. No microservices, no message brokers.
Per-Group Isolation
Each group gets its own container, filesystem, IPC namespace, and Claude session. Groups cannot access other groups' data.
Concurrency Control
GroupQueue limits concurrent containers (default: 3). Per-group FIFO ordering with retries on failure using exponential backoff.
IPC via Filesystem
Containers communicate with the host through JSON files in per-group directories. The host polls, validates authorization, executes, and cleans up.
Key Files
index.ts — Orchestrator — polling loop, message processing, agent invocation container-runner.ts — Spawns containers with isolated mounts, streams output group-queue.ts — Per-group FIFO queue with concurrency limits and retry backoff ipc.ts — Processes container IPC requests with authorization checks db.ts — SQLite — messages, sessions, groups, tasks, router state task-scheduler.ts — Cron, interval, and one-shot scheduled task execution Philosophy
The principles that shape every NanoClaw decision.
Small enough to understand
NanoClaw is one process, a handful of source files. Small enough that you can read and understand the entire codebase.
Secure by isolation
Agents run in Linux containers. They can only see what's explicitly mounted. Bash is safe because it runs inside the container.
Built for one user
NanoClaw isn't a monolithic framework. It's working software that fits your exact needs. Fork it, have Claude Code make it match yours.
AI-native
No installation wizard; Claude Code guides setup. No dashboard; ask Claude. No debugging tools; describe the problem.
Skills over features
Contributors add Claude Code skills like /add-telegram that transform your installation. You end up with clean code that does exactly what you need.
Best harness, best model
Runs on Claude Agent SDK, which means you're running Claude Code directly. The harness matters. A good one gives smart models superpowers.
Get Started with NanoClaw in 3 Lines
Clone NanoClaw, enter the directory, and let Claude handle the rest.
$ git clone https://github.com/qwibitai/nanoclaw.git
$ cd nanoclaw
$ claude Then run /setup Claude Code handles everything: dependencies, authentication, container setup, service configuration.