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.
This commit is contained in:
Tony0410
2026-08-15 22:21:32 +08:00
parent 92e8028bb8
commit c8565c62ac
8 changed files with 467 additions and 0 deletions
+70
View File
@@ -0,0 +1,70 @@
---
title: QwenPaw
type: system
status: active
created: 2026-08-15
updated: 2026-08-15
verified_on: 2026-08-15
confidence: medium
tags: [qwenpaw, ct465, agent, paseo]
sources: [skill-inspection, config-reference]
---
# QwenPaw
## Purpose
Multi-agent gateway platform. Runs on CT465 with its own workspace, agent profiles, and model routing. Used for group chats and specialised agent tasks.
## Location
- **Container:** LXC CT465 (`qwenpaw`)
- **Hostname:** `qwenpaw`
- **Software:** QwenPaw with Paseo daemon
## Current State
- **Status:** Active
- **Default chat model:** OmniRoute Smart Route (`auto/smart`)
- **Config format:** JSON (`agent.json` per workspace)
- **Daemon:** `paseo.service`
## Operating Layers
QwenPaw has several layers that must not be conflated:
1. **PVE/LXC layer:** container status, guest access, resources
2. **Paseo layer:** long-running daemon/supervisor (`paseo.service`)
3. **Workspace layer:** agent profiles with `agent.json` and `active_model`
4. **Provider layer:** remote providers (Kilo/OpenRouter) or local (Ollama)
5. **Channel layer:** Telegram or other messaging adapters
## Key Rules
- **Do not assume "process is running" means "agent works."** Model resolution and a real response are separate checks.
- **Verify model resolution per agent.** A default agent can work while a specialist agent silently has no model.
- **Preserve existing provider/model routes.** Do not repin unrelated agents or replace known-good routes.
- **Default chat model:** Use OmniRoute Smart Route (`auto/smart`) per Anthony's preference.
## Diagnostics
```bash
qwenpaw doctor --deep --timeout 10 --llm-timeout 20
qwenpaw models list
qwenpaw daemon status
```
## Provider Verification
When adding an OpenAI-compatible provider from Proxmox:
- Verify target by VMID and hostname before writing config
- CT600/`omniroute` is the OmniRoute service at `100.88.81.19:20128`
- CT601/`omni` is a separate guest at `100.93.204.4`
- Query `/v1/models` using the exact API key stored for QwenPaw, not a management key
## Related
- [[agents/hermes-production]] — Production Hermes
- [[systems/omniroute]] — Model routing
- [[systems/model-providers]] — Provider catalog
- [[infrastructure/proxmox]] — PVE host