Files
agent-estate-wiki/agents/qwenpaw.md
T
hermes d981e30128 stocktake(2026-10-11): skills-index 346 skills/70 cats; freshness 62 stale/24 fresh/7 no-date; 5 live-drift corrections
Drift found and corrected against live sources (not guessed):
- OmniRoute: CT600 omniroute is RUNNING and serving :20128 (combo API live);
  CT601 omni is STOPPED with onboot=0 (peer offline 54d). Wiki had these inverted.
  Hermes custom:omni resolves to omniroute -> CT600, not CT601.
- Third OmniRoute node discovered: omniroute-1 at 100.78.63.20:20128, live (401),
  registered as custom provider omni-101 (5384 models, default smart-route,
  carries skills_hub/free-stack). Not in pct list; identity unconfirmed.
- Ignis: TWO live instances. CT460 ignis (:8080, vault wiki/agent-estate-wiki) and
  CT200 ignis-ignis-1 (image ignis-server:latest, host 8092, vault /opt/ignis/vaults).
  Both return HTTP 200. Page now distinguishes them.
- Tailscale: /agent-estate targets bare 127.0.0.1:8769 (was .../8769/agent-estate-role-dashboard.html);
  undocumented tailnet-only :9443 -> 127.0.0.1:5173 added; CT201 routes corrected
  (8085 targets + /steel 5173 + /steel-api 3000, replacing the wrong :8443 -> :8082 row).
- Proxmox: rebuilt from live pct list + qm list. Added CT475 agentzero and VM110 omarchy
  (both previously missing); 282 ubuntu-server-xfce corrected to stopped; dead rows removed.
  VM403 open-claw and VM401 hermes-old absent from qm list - flagged unconfirmed, not deleted.
- Nanobot: gateway nanobot-gateway (PID 2259048) alive on 8765/8766. It is NOT systemd
  nanobot.service/gateway.service (both return inactive - wrong unit names). Port 8900
  no longer listening; "Serve API" claim flagged unverified.
- Docker: old "runtime not available" was a CT460 socket artifact (root:docker srw-rw----,
  hermes not in group docker, no passwordless sudo in cron). Documented CT200 (~50 containers),
  CT333 (9 containers), CT460 via sudo.
- Mattermost CT255 confirmed stopped; matches Tailscale peer offline 21d.

Flagged, not investigated (no root cause):
- mycompose-db-1 on CT200 is in Restarting (1) - crash-looping.

62 pages remain >21d stale and were NOT rewritten this pass (concepts, decisions,
comparisons, most runbooks) - not probed against a live source, so reported not faked.
Quartz rebuild step still inert (no quartz.config.ts) - public/ not refreshed.

Artifacts: systems/skills-index.md regenerated, raw/stocktake/freshness-20261011.txt.
2026-10-11 03:11:07 +08:00

2.7 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
QwenPaw system active 2026-08-15 2026-10-11 2026-10-11 high
qwenpaw
ct465
agent
paseo
live-probe
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 — paseo.service active on CT465, verified 2026-10-11
  • Default chat model: OmniRoute Smart Route (auto/smart)
  • Config format: JSON (agent.json per workspace)
  • Daemon: paseo.service
  • Also listening on CT465: PVE exporter (100.96.150.69:9221), a Python service on :9876, and local SMTP :25
  • CT400/CT465 identity: confirmed CT465 = qwenpaw, running

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

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 live OmniRoute service at 100.88.81.19:20128 — verified serving 2026-10-11
  • CT601/omni is a separate guest at 100.93.204.4 — stopped, do not use
  • A third instance omniroute-1 at 100.78.63.20:20128 is also live; Hermes registers it as provider omni-101
  • Query /v1/models using the exact API key stored for QwenPaw, not a management key
  • See systems/omniroute for the full live node table