- 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
4.1 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-11-11 | 2026-11-11 | 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.
Guest lists re-probed 2026-11-11 — VM 403 and VM 401 still absent, and the estate shrank a little more.
qm listonpve(100.96.100.82) now shows only VMs 100, 101, 110, 282 (VM 310 has gone since the 2026-10-19 probe listed it), andpct listshows CTs 103, 200, 201, 205, 207, 209 (stopped), 215, 255, 270, 299 (stopped), 333, 450, 460, 465, 475, 555 (stopped), 600 — CT 601 is gone. Live CT names:205 ollama,333 clawtest,450 hermesagent,600 omniroute.m93pwas not re-probed this pass; its 2026-10-20 list stands. ZeroClaw is running on CT333 (PID 142,--allow-degraded-security).
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