--- title: ZeroClaw type: system status: active created: 2026-08-15 updated: 2026-11-11 verified_on: 2026-11-11 confidence: high tags: [zeroclaw, ct333, daemon, agent] sources: [skill-inspection, config-reference] --- # ZeroClaw ## Purpose Autonomous AI daemon running on CT333. Handles independent agent operations with TOML configuration. Runs alongside Nanobot on the same container but is completely separate software. ## Location - **Container:** LXC CT333 (`clawtest`) - **Tailscale IP:** `100.122.189.81` - **User:** root - **Shares container with:** [[agents/nanobot]] ## Current State - **Status:** Active - **Config format:** TOML (`/root/.zeroclaw/config.toml`) - **Daemon binary:** `/root/.local/bin/zeroclaw daemon` - **Workspace:** `/root/.zeroclaw/workspace` - **State:** `/root/.zeroclaw/state/` > **Re-verified 2026-10-20 — running as documented, with one path nuance.** > The daemon **is** live on CT333: `pgrep -af zeroclaw` → `136 /usr/local/bin/zeroclaw daemon > --allow-degraded-security` (PID 136, up since boot). Note the process runs > **`/usr/local/bin/zeroclaw`**, which is a **symlink → `/root/.cargo/bin/zeroclaw`** — a *third* > path alongside the `/root/.local/bin/zeroclaw` binary named above (that file also exists, 37 MB). > The `--allow-degraded-security` flag was **not** recorded on this page previously; it is part of > the live command line. > `/root/.zeroclaw/` contains `config.toml` plus ~15 dated `config.toml.bak*` snapshots. > **Re-verified 2026-11-11 — running as documented.** `pct exec 333 -- pgrep -af zeroclaw` returns > `142 /usr/local/bin/zeroclaw daemon --allow-degraded-security` (PID has rotated from 136, up > since boot). `/usr/local/bin/zeroclaw` is the live path; `/root/.local/bin/zeroclaw` also exists. > CT333 is named **`clawtest`** in `pct list` and `pct exec 333 -- hostname` returns `clawtest` — > so the `clawtest` label on this page is correct, and the contrary claim on > [[comparisons/hermes-vs-nanobot]] has been corrected. ## Key Paths | Item | Path | |------|------| | Config | `/root/.zeroclaw/config.toml` | | Config dir | `/root/.zeroclaw/` | | Daemon binary | `/root/.local/bin/zeroclaw` | | Workspace | `/root/.zeroclaw/workspace` | | State | `/root/.zeroclaw/state/` | ## Access ```bash sshpass -p 'admin' ssh -o StrictHostKeyChecking=no root@192.168.178.39 "pct exec 333 -- " ``` ## Critical Pitfalls - **Duplicate daemons break Telegram replies.** If Telegram shows typing then no message, check for multiple daemon processes before changing providers. - **Do not confuse with Open-Claw.** Open-Claw is VM 403, not CT333. Different config format (TOML vs JSON), different user (root vs openclaw), different auth (paired tokens vs password). - **Do not confuse with Nanobot.** Nanobot is JSON config, ZeroClaw is TOML. Both on CT333 but completely separate. ## Scope Discipline - No destructive operations without confirmation - No modifying running state without saving config first - No changes that could create lock-out scenarios without a safety net ## Related - [[agents/nanobot]] — Different agent, same container - [[agents/open-claw]] — Different VM, similar name - [[infrastructure/proxmox]] — PVE host