NanoClaw packaged as a Telegram-first All-In-One Unraid container.
nanoclaw-aio wraps the official NanoClaw Telegram fork with the official native credential proxy patch so the stack can run from a single Unraid container without needing a separate OneCLI service. The image keeps the NanoClaw code immutable inside the container and persists only runtime state under /appdata, which makes upgrades much safer than mounting the whole project directory.
- A single-container
ghcr.io/jsonbored/nanoclaw-aio:latestimage - Explicit image tags matching the pinned upstream NanoClaw Telegram version, plus
latestandsha-... - An Unraid CA template at nanoclaw-aio.xml
- A local smoke test at scripts/smoke-test.sh
- Upstream version tracking via upstream.toml and scripts/check-upstream.py
- Automated
awesome-unraidsync for the XML
- Official
qwibitai/nanoclaw-telegramcode pinned to a specific upstream commit - Official native credential proxy patch applied so Anthropic credentials can stay in
.env - Telegram main-chat auto-registration on first boot
- Persistent NanoClaw state under
/appdata - Docker socket access so NanoClaw can launch isolated agent containers
- This image is currently packaged and validated for
linux/amd64. - There is no web UI. NanoClaw is controlled through Telegram.
/appdatapersists groups, database state, credential-proxy config, sessions, and task data./var/run/docker.sockmust be mounted so NanoClaw can start agent containers.TELEGRAM_BOT_TOKENandTELEGRAM_CHAT_IDare required for a real working deployment. If they are missing, the container stays up in a waiting-for-config state instead of crash-looping.
- Install the Unraid template.
- Set
ANTHROPIC_API_KEY,TELEGRAM_BOT_TOKEN, andTELEGRAM_CHAT_ID. - Keep
AUTO_SETUP_TELEGRAM=trueunless you want to register groups manually later. - Mount the Docker socket.
- Start the container and watch the logs for first-boot registration.
Local validation completed on March 29, 2026:
- explicit
linux/amd64Docker build succeeded - local smoke test passed end-to-end in bootstrap mode
- restart and persistence coverage added for
/appdata - build/security workflows were hardened with pinned action SHAs and upstream tracking
- the wrapper was rebuilt around the official
qwibitai/nanoclaw-telegramupstream instead of cloning an unpinned unrelated repo
- Issues: JSONbored/nanoclaw-aio issues
- Upstream app: qwibitai/NanoClaw
- Upstream Telegram fork: qwibitai/nanoclaw-telegram
If this work saves you time, support it here: