nanoclaw
NanoClaw is a self-hosted personal AI assistant that orchestrates Claude Agent SDK-based agents inside isolated Linux containers, providing multi-channel messaging (e.g., WhatsApp/Telegram/Slack/Discord/Gmail), per-group memory and filesystem isolation, and scheduled/recurring tasks. It’s designed to be customized by modifying code and by adding “skills” (Claude Code skills) rather than using configuration-heavy setups.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
README claims agents run in Linux containers with filesystem isolation and explicit mounts, and that outbound credentials do not enter containers (routed via OneCLI’s Agent Vault with per-agent policies and rate limits). However, TLS enforcement for all network paths and concrete authentication/authorization scope granularity are not evidenced in the provided materials. Dependency security posture cannot be verified from the given manifest alone (only a few dependencies are listed).
⚡ Reliability
Best When
You want to self-host an agent runtime with container filesystem isolation and you’re comfortable using Claude Code skills and customizing a fork.
Avoid When
You need a stable public API/SDK for third-party automation, or you cannot operate Docker/containers and handle local secrets/configuration via environment variables and related tooling.
Use Cases
- • Run a private Claude-based assistant with isolated per-group context and memory
- • Automate recurring tasks (e.g., weekly briefings, scheduled updates) that can message you
- • Connect an assistant to one or more messaging channels (WhatsApp/Telegram/Slack/Discord/Gmail) via skills
- • Give agents controlled access to mounted directories (e.g., an Obsidian vault folder) for retrieval and writing
- • Use Claude Agent SDK containerized execution for better host isolation than in-process permission checks
Not For
- • A managed SaaS you can drop into without hosting or container/runtime setup
- • A turnkey enterprise contact-center or fully multi-tenant platform with centralized admin/monitoring
- • Use cases requiring a stable, documented external HTTP API surface for programmatic integration (it appears to be primarily an agent runtime/CLI workflow)
Interface
Authentication
Authentication appears to be primarily local/secrets-based for model endpoints and per-channel credentials via the documented skills/setup flow; outbound requests reportedly route through OneCLI’s Agent Vault for per-agent policies and rate limits.
Pricing
README describes self-hosting; no pricing tiers are provided in the supplied materials. Cost will depend on your LLM usage and messaging provider costs.
Agent Metadata
Known Gotchas
- ⚠ This project is primarily operated via Claude Code skills/CLI flow; integration as a generic automated API may require additional work.
- ⚠ Skills modify a fork; agent workflows may be sensitive to local skill configuration and mounted directory permissions.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for nanoclaw.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-29.