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: 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/
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
sshpass -p 'admin' ssh -o StrictHostKeyChecking=no root@192.168.178.39 "pct exec 333 -- <command>"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