Single-process message loop + per-group queues
A single Node process polls and routes inbound messages into per-group queues, then applies a global concurrency cap so execution is predictable and contexts do not cross-contaminate.
NanoClaw is a personal AI assistant that is intentionally small enough to understand end-to-end. It places the agent inside real Linux containers so the trust boundary is OS isolation, not application-level permission toggles. Built with TypeScript and Node.js as a single-process orchestrator, it uses WhatsApp as the primary channel to drive chat triggers, scheduled jobs, tool execution, and memory writes in one tight loop. State and memory are local-first via SQLite for messages, groups, and sessions, while each group runs with its own isolated filesystem context. Setup is AI-native: Claude Code guides dependencies, auth, and container runtime wiring so you can self-host a private assistant on your own hardware.
| ✕Traditional Pain Points | ✓Innovative Solutions |
|---|---|
| Running agents directly on the host makes it hard to be secure-by-default; a prompt mistake can touch real files and commands. | NanoClaw treats containers as the first security boundary—using Docker or Apple Container for filesystem isolation so tools run inside a controlled sandbox. |
| General-purpose assistants often grow into dependency-heavy systems that are difficult for one person to audit and customize. | A minimal single-process design keeps the message loop, scheduler, memory store, and container runner on the shortest path, while skills-based changes avoid bloating the core. |
1node --version # v20.x; docker --version # Docker on macOS/Linux; Apple Container optional on macOS1git clone https://github.com/qwibitai/nanoclaw.git && cd nanoclaw1claude1# Follow Claude Code prompts: setup / debug; verify WhatsApp connectivity and scheduler runs| Core Scene | Target Audience | Solution | Outcome |
|---|---|---|---|
| Security-first private WhatsApp assistant | individuals and indie builders | trigger summaries and automations via WhatsApp while tools run inside containers | self-hosted automation with a safer trust boundary |
| Group-isolated family/team helper | families or small teams | each group gets isolated memory and filesystem context plus scheduled briefings | long-running assistance without cross-group context leakage |
| Minimal, auditable ops automation agent | engineers offloading repetitive tasks | encode recurring workflows as scheduled jobs | controlled execution via readable code and container isolation |
