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 |
|---|---|---|---|
| hermes-production | CT460 | Production Command Centre | Active |
| hermes-chaos | CT450 | Experimental Chaos Lab | Active |
| nanobot | CT333 | Scout (quota notifications, daily briefing) | Active |
| qwenpaw | CT465 | Multi-agent gateway | Active |
| zeroclaw | CT333 | Autonomous daemon (TOML config) | Active |
| open-claw | VM 403 | Autonomous gateway node | Active |
Shared Infrastructure
All agents share:
- omniroute — model routing and provider management
- model-providers — LiteLLM + OmniRoute provider catalog
- proxmox — PVE host and containers
- tailscale — VPN and serve routes
- 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
- hermes-agent — Hermes Agent system details
- nanobot — Nanobot system details
- hosts — Host and container inventory