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.
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.
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