claudeclaw-plus ghcr.io/paulmeier/claudeclaw-plus-container:latest https://github.com/paulmeier/claudeclaw-plus-container/pkgs/container/claudeclaw-plus-container bridge false sh --restart=unless-stopped https://github.com/paulmeier/claudeclaw-plus-container-unraid/issues https://github.com/paulmeier/claudeclaw-plus-container AI: https://raw.githubusercontent.com/paulmeier/claudeclaw-plus-container-unraid/main/icons/claudeclaw-plus-container.png https://raw.githubusercontent.com/paulmeier/claudeclaw-plus-container-unraid/main/templates/claudeclaw-plus-container.xml http://[IP]:[PORT:4632] ClaudeClaw+ is a superset of claudeclaw that adds a governance and policy layer, durable multi-step orchestration, persistent cross-session memory, and a hardened web UI on top of the upstream daemon. Everything in vanilla claudeclaw is here too — Telegram, Discord, and Slack bridges, scheduled cron jobs, voice transcription via Whisper, and a web dashboard. Requires a Claude Code subscription at claude.ai/code — no API key needed. A Claude Code subscription (claude.ai/code) is required. After starting the container for the first time, open a terminal to it and run: claude login claude ai assistant llm telegram discord slack whisper voice cron jobs automation governance orchestration memory 4632 1 /mnt/user/appdata/claudeclaw-plus /root/.claude/tailscale ClaudeClaw+ extends Claude Code into a personal AI assistant daemon that runs continuously in the background. It is a superset of upstream claudeclaw, syncing from it daily and adding a governance and policy layer, durable multi-step orchestration (DAG-style jobs that survive restarts), persistent cross-session memory, and a hardened web UI. AUTHENTICATION — REQUIRED BEFORE USE: ClaudeClaw+ uses your Claude Code subscription, not an API key. After starting the container for the first time, open a terminal to the container in Unraid and run: claude login This opens an OAuth browser flow. Complete it once and your credentials are saved to the app data directory. They persist across container restarts. CONFIGURATION: On first start, a default settings.json is created at your app data path under claudeclaw/settings.json. ClaudeClaw+ inherits the upstream settings schema, plus its own keys for governance, model routing, orchestration, and persistent memory. See https://github.com/TerrysPOV/ClaudeClaw-Plus for the full Plus-specific configuration reference. MESSAGING SETUP: Telegram — add your BotFather token and allowed user IDs to settings.json. Discord — add your bot token, enable Message Content Intent in the developer portal, and add channel IDs. Slack — add your xoxb- bot token and xapp- app-level token (Socket Mode required). All messaging bridges use outbound connections only — no additional ports need to be opened. ADDITIONAL DIRECTORIES: Mount host directories under /root/ inside the container (e.g. /root/notes, /root/projects) so they fall within ClaudeClaw+'s default 'moderate' security scope. Paths outside /root/ are invisible to the daemon unless you set settings.json security.level to 'unrestricted'. Use read-only mode for directories it should only read, read-write for those it can modify. BACKUPS: Mount a backup directory and run /backup.sh inside the container to create a timestamped snapshot. RUNNING ALONGSIDE VANILLA claudeclaw: Both containers can run side-by-side on the same Unraid box. The container name and default appdata path (/mnt/user/appdata/claudeclaw-plus vs /mnt/user/appdata/claudeclaw) are distinct, and each gets its own web dashboard. If you want them on the same port externally, change one of the Web Dashboard Port mappings.