Files
agent-estate-wiki/agents/zeroclaw.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

83 lines
3.2 KiB
Markdown

---
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 -- <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
## Related
- [[agents/nanobot]] — Different agent, same container
- [[agents/open-claw]] — Different VM, similar name
- [[infrastructure/proxmox]] — PVE host