3.5 KiB
title, type, status, created, updated, verified_on, confidence, tags
| title | type | status | created | updated | verified_on | confidence | tags | |||
|---|---|---|---|---|---|---|---|---|---|---|
| Agent Estate | system | active | 2026-08-15 | 2026-10-20 | 2026-10-20 | high |
|
Agent Estate
Map of all AI agents, their locations, and their roles in Anthony's setup.
Overview
The agent estate consists of multiple Hermes instances, a QwenPaw deployment, ZeroClaw, Open-Claw, and Nanobot — each with a defined role and home container.
Agents
| Agent | Container | Role | Status |
|---|---|---|---|
| agents/hermes-production | CT460 | Production Command Centre | Active |
| agents/hermes-chaos | CT450 | Experimental Chaos Lab | Active |
| agents/nanobot | CT333 | Scout (quota notifications, daily briefing) | Active |
| agents/qwenpaw | CT465 | Multi-agent gateway | Active |
| agents/zeroclaw | CT333 | Autonomous daemon (TOML config) | Active |
| agents/open-claw | VM 403 | Autonomous gateway node |
Note: Open-Claw (VM 403) is not present
Live probe on 2026-10-19 (pct list + qm list on PVE host 100.96.100.82) shows no VM 403 and no VM 401. The QEMU VMs on the host are 100, 101, 110, 282, 310. The open-claw and zeroclaw pages still document the intended configuration (from 2026-08-15), but the VM is currently absent — treat agents/open-claw.md as stale/unverified until the VM is recreated or a new location is documented.
Extended to the second PVE host on 2026-10-20. m93p (100.104.51.98) was probed as well and
also has no VM 403 (its LXC guests are 100, 101, 102, 104, 105, 221, 245, 500, 998, 1006, 1007,
1008, 1241, 1260, 1261, 1262, 1263, 1264). The tailscale status peer list contains no
open-claw node either. Open-Claw is therefore absent from the whole estate, not just relocated.
ZeroClaw, by contrast, was re-verified live on 2026-10-20 and is running on CT333
(/usr/local/bin/zeroclaw daemon --allow-degraded-security, PID 136) — see agents/zeroclaw.
Shared Infrastructure
All agents share:
- systems/omniroute — model routing and provider management
- systems/model-providers — LiteLLM + OmniRoute provider catalog
- infrastructure/proxmox — PVE host and containers
- infrastructure/tailscale — VPN and serve routes
- infrastructure/domains-and-tunnels — Cloudflare Tunnel routing
Relationships
- Hermes production (CT460) and Hermes Chaos (CT450) are separate Hermes instances with separate configs, skills, and cron jobs.
- ZeroClaw and Nanobot share the same LXC container (CT333) but are different software with different configs (TOML vs JSON).
- Open-Claw (VM 403) is a completely separate Docker-based gateway, not related to ZeroClaw despite the similar name.
- QwenPaw (CT465) is a separate agent platform with its own workspace and model routing.
Key Rules
- Never assume one agent's config applies to another. Each agent has its own config format, paths, and provider routing.
- CT333 has two agents. ZeroClaw (root, TOML) and Nanobot (JSON) coexist. Do not restart one without checking the other.
- CT450 Chaos is experimental. Changes here must not affect CT460 production without explicit approval.
- Phase Two (estate consolidation) is not approved. CT450 duplicate cron jobs remain paused; CT460 counterparts remain enabled.
Related
- systems/hermes-agent — Hermes Agent system details
- systems/nanobot — Nanobot system details
- infrastructure/hosts — Host and container inventory