BitCryptic

[Support] NanoClaw — Lightweight Secure AI Agent for Unraid (DEPRECATED)This template is no longer supported. See the announcement below. NanoClaw is a lightweight, open-source personal AI agent that runs securely on your own server. It connects to Matrix and Telegram (via skill) and runs every agent session inside its own isolated Docker container — so the AI only sees what you explicitly give it access to. Built as a minimal alternative to OpenClaw/Clawdbot, NanoClaw has ~15 source files you can actually read and understand. No complex config files — customise by telling Claude Code what you want changed. Features Matrix (E2EE) channel support — Telegram available via skill install; WhatsApp, Slack, Discord in development Per-conversation isolated Docker containers — true OS-level sandbox, not application-level permissions Scheduled tasks — morning briefings, weekly reviews, automated reports Web search and fetch built in Agent Swarms — spin up teams of specialised agents that collaborate Per-group memory via CLAUDE.md files Anthropic API key authentication (console.anthropic.com) Requirements Anthropic API key from console.anthropic.com — or a local model via per-group provider override (NANOCLAW_PROVIDER_BASE_URL + NANOCLAW_PROVIDER_API_KEY + NANOCLAW_PROVIDER_MODEL). Note: Claude Code OAuth tokens are no longer supported for automated/non-interactive use — CLAUDE_CODE_OAUTH_TOKEN will not produce a working agent. Matrix: Homeserver URL, bot user ID, and access token for a dedicated bot account Telegram: Bot token from @BotFather (optional — requires skill install, see NanoClaw changelog) At least one channel (Matrix or Telegram) must be configured Docker socket access (required — NanoClaw spawns isolated agent containers for each conversation) Installation Install via Community Applications and search for NanoClaw, or drop the template XML directly into /boot/config/plugins/dockerMan/templates-user/ on your Unraid server. Required fields: HOST_PROJECT_ROOT — must match the host path of your AppData volume. The template defaults to /mnt/cache/appdata/nanoclaw but this must reflect where Unraid has actually placed the appdata on your system. If your cache pool or appdata share is configured differently, it may be /mnt/user/appdata/nanoclaw or another path. Verify with ls /mnt/cache/appdata/nanoclaw — if that returns nothing, adjust accordingly. A path mismatch here will cause agent containers to silently fail to spawn. ANTHROPIC_API_KEY — required, from console.anthropic.com Telegram (optional, via skill): TELEGRAM_BOT_TOKEN from @BotFather Matrix (optional): MATRIX_HOMESERVER_URL, MATRIX_BOT_USER_ID, MATRIX_ACCESS_TOKEN MATRIX_BOT_PASSWORD — k2's Matrix account password, used once on first startup to bootstrap cross-signing keys (eliminates the "unverified device" warning in Element X). After the first successful start, the bootstrap is skipped automatically — safe to leave set or remove. Recommended: NANOCLAW_DOCKER_NETWORK — set to your Docker network name (e.g. ai-local) if you run Ollama, LiteLLM, or Paperclip on the same server. Without this, agent containers use the default bridge network and cannot reach those services by hostname. At least one channel (Matrix or Telegram) must be configured. After starting the container: Matrix: Invite your bot account to a room The room auto-registers on first message Send @Andy hello — Andy will respond Telegram (after skill install): Send /chatid to your bot The bot will reply with your chat ID and automatically register Send @Andy hello — Andy will respond The trigger word is @Andy by default (configurable via NANOCLAW_TRIGGER). To customise NanoClaw (change trigger word, add scheduled tasks, connect integrations), clone the repo and run claude in the project directory — Claude Code handles all configuration changes conversationally. Links Template repository: https://github.com/bitcryptic-gw/unraid-nanoclaw Add to CA directly: https://raw.githubusercontent.com/bitcryptic-gw/unraid-nanoclaw/main/NanoClaw.xml NanoClaw project: https://github.com/qwibitai/nanoclaw Docker Hub image: https://hub.docker.com/r/bitcryptic/nanoclaw Notes The Docker socket mount (/var/run/docker.sock) is required — NanoClaw uses it to spawn isolated agent containers for each conversation. This is the same pattern used by Portainer, Watchtower, and similar tools. Port 3001 is the internal credential proxy used by agent containers. It only needs to be accessible on the local Docker bridge network — you do not need to expose it externally. NanoClaw stores its data in four directories under AppData: data/, store/, groups/, and logs/. Post any issues or questions here and I'll do my best to help. Changelogv1.3.0 (2026-04-20) OneCLI credential support — NanoClaw now supports OneCLI as the core credential gateway for agent containers, aligned with upstream's architecture. Two new optional template variables: ONECLI_URL and ONECLI_API_KEY. Leave blank if you prefer the self-hosted native credential proxy (install the use-native-credential-proxy skill instead) Telegram removed from core — Telegram channel code has moved to the upstream qwibitai/nanoclaw-telegram skill repo, consistent with upstream's channel extraction architecture. Telegram remains fully functional via skill install; the bot token variable is retained in the template for compatibility New MCP skills — Vikunja task management skill added (VIKUNJA_URL, VIKUNJA_TOKEN). UnraidClaw, Tailscale, and Home Assistant skills stabilised and skill-files-only (env forwarding via template variables) Trigger matching tightened — trigger word must now appear at the start of a message (^@trigger) rather than anywhere in the message body Writable global memory mount — main agent now has write access to /workspace/global, fixing silent failures when Andy attempts to write global memory notes v1.2.55 (2026-04-10) Telegram is now optional — Matrix-only setups no longer require a Telegram bot token Fixed MCP skill credentials (Ollama, Home Assistant, Tailscale, UnraidClaw) not reaching agent containers — all integrations now work correctly out of the box New variable: NANOCLAW_DOCKER_NETWORK — set to your Docker network name (e.g. ai-local) to allow agent containers to reach Ollama, LiteLLM, and Paperclip by hostname. Defaults to ai-local in the template New variable: MATRIX_BOT_PASSWORD — used once at startup to bootstrap Matrix cross-signing keys, eliminating the "unverified device" warning in Element/Element X. Safe to leave set; bootstrap is skipped automatically after the first run Matrix room cleanup: NanoClaw no longer auto-joins unregistered rooms on startup v1.2.49 (2026-04-08) Matrix channel support with full E2EE (Rust crypto store, SQLite persistence across restarts) Telegram channel restored and stabilised ANTHROPIC_API_KEY now automatically injected into new group sessions — fresh installs no longer require manual file editing Matrix channel vars added to Unraid CA template v1.2.25 (2026-03-16) /chatid command now auto-registers the chat — no manual SQLite setup required Fresh installs work out of the box — no need to copy .claude.json from another machine Stale sessions cleared automatically on container restart/update Fixed agent container file ownership issues that caused silent failures Docker socket mount corrected from Device to Path type (fixes Unraid compatibility) Multi-arch image (amd64 + arm64) on Docker Hub

A Pi Network Node for inclusion...hope I've landed at the right place for this to be considered. https://raw.githubusercontent.com/bitcryptic-gw/unraid-pi-network-node/main/PiNetworkNode.xml

Template has been updated to latest docker image, includes required version increase as of 1st March 2026 for Pi Network nodes.

Please consider including this in Unraid' CA

I'm maintaining an Unraid Community Applications (CA) template for running the Pi Network Node on Unraid (mainnet), via the BitCryptic wrapper image with performance tuning baked in. Repo (template + docs): https://github.com/bitcryptic-gw/unraid-pi-network-node Docker Hub: https://hub.docker.com/r/bitcryptic/pi-network-node Install via Community Applications — search for "Pi Network Node", or add this repository manually in CA settings: https://raw.githubusercontent.com/bitcryptic-gw/unraid-pi-network-node/main/PiNetworkNode.xml What the BitCryptic wrapper adds The template uses bitcryptic/pi-network-node rather than the upstream image directly. This bakes in three performance tuning env vars that significantly reduce CPU load on the host: - INGEST_DISABLE_STATE_VERIFICATION=true — disables periodic full ledger state scans (main CPU reduction) - PARALLEL_JOB_SIZE=1 — reduces horizon ingestion worker parallelism - HISTORY_RETENTION_COUNT=1000000 — retains ~8 weeks of ledger history instead of full history since genesis The latest tag always tracks the current Pi node release. Versioned tags (e.g. v22.1) are also available for pinning. Template notes - Persistent data: required mapping to /opt/stellar (Unraid appdata recommended) - Ports mapped (standard): 31401 (Horizon HTTP), 31402 (stellar-core peer), 31403 (local history / webfsd) - Required env var: POSTGRES_PASSWORD - Optional env var: NODE_PRIVATE_KEY (migration only — do not run two nodes with the same key) - Mainnet flags passed as Post Arguments: --mainnet --enable-auto-migrations If you need help, please include: - Unraid version - Container startup log (first ~200 lines after start) - docker ps --format '{{.Names}}\t{{.Ports}}' - Your /opt/stellar host path mapping Disclaimer: Community-maintained template; not affiliated with or endorsed by Pi Core Team.