Files
agent-estate-wiki/agents/zeroclaw.md
T

2.6 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
ZeroClaw system active 2026-08-15 2026-10-20 2026-10-20 high
zeroclaw
ct333
daemon
agent
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.

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