Files

T

Tony0410 c8565c62ac feat: add agent estate section with 7 pages

Add agents/ directory with comprehensive documentation for all agents:
- agents/index.md — estate map and relationships
- agents/hermes-production.md — CT460 production Command Centre
- agents/hermes-chaos.md — CT450 experimental Chaos Lab
- agents/nanobot.md — CT333 Scout (quota notifications)
- agents/qwenpaw.md — CT465 multi-agent gateway
- agents/zeroclaw.md — CT333 autonomous daemon (TOML)
- agents/open-claw.md — VM 403 autonomous gateway

Updated index.md with Agent Estate section and links.
All pages follow existing SCHEMA.md conventions with YAML frontmatter.

2026-08-15 22:21:32 +08:00

2.0 KiB

Raw Blame History

title, type, status, created, updated, verified_on, confidence, tags, sources

title

type

status

created

updated

verified_on

confidence

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/

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

agents/nanobot — Different agent, same container
agents/open-claw — Different VM, similar name
infrastructure/proxmox — PVE host

2.0 KiB Raw Blame History