wiki-maintain.sh ran clean (302 skills indexed, Quartz rebuilt, 634 files emitted,
service restarted). The freshness report listed 8 stale pages; each was diffed
against live state and corrected only where reality could be verified. A second
script run rewrote the same-day report with 0 stale / 103 fresh / 4 no-date,
so the committed report matches the tree it ships with.
- infrastructure/hosts.md: CT600 is LIVE (not retired); CT601 does not exist on
either hypervisor; CT333 verified running; both hypervisors verified; config
33->51; skills 66->302; cron 25->28 (25 enabled / 3 disabled); Xvfb :102->:99;
providers split into Omniroute:20128 (CT600) and omni-101 (CT101, default).
- agents/hermes-production.md: Tailscale IP 100.96.100.82 -> 100.118.5.51 (the
old value is the PVE hypervisor); v0.21.5 -> v0.22.3; dead 8082 claim removed;
fallback chain rewritten from live config (first entry is the dead nous
credential); all 8 auxiliary slots now no-think/freeapi/auto; cron 30->28.
- agents/hermes-chaos.md: v0.22.3 (same build as CT460); "3 commits behind" ->
0 behind origin/master; default model smart-route on custom:omni-101; cron
"11 paused" -> 25 jobs (13 enabled / 12 disabled), 9 names shared with CT460.
- infrastructure/tailscale.md: node table rebuilt from status --json; octoagent
and omarchymac-1 were missing entirely (52 -> 54 non-funnel nodes); m93p now
online; every offline age refreshed; omni row corrected to "CT601 removed
from both hypervisors"; Serve tables re-probed per host.
- systems/memory-backend.md: re-verified against live config; coverage 1899/2350
(80.8%), working 96.8%, episodic 99.4% — above the 95% reindex threshold.
- runbooks/provider-health.md: the step-3 OmniRoute snippet raised IndexError
(provider renamed omniroute -> Omniroute:20128; key moved to key_env) — fixed;
new step 3b documents the omni-101 /v1/models false-failure quirk.
- runbooks/update-hermes-safely.md: added managed-runtime dependency re-assert
step; clarified --branch vs stable channel (v0.22.5 available).
- incidents/2026-10-03-ct450-hermes-update.md + incidents/2026-10-03-mnemosyne-vector-recall-fts-only.md:
Current-state sections recording current versions and embedding coverage.
All 9 corrected pages verified 200 at http://127.0.0.1:9120/<path>.
Vault mirror at /home/hermes/wiki synced for all touched files (22 copies,
sha256-verified) and committed locally; the vault is local-only and is not pushed.
No secrets written — IDs, URLs, key env var names, counts and timestamps only.
Primary personal agent for Anthony. Runs automation, research, communication, knowledge management, browser control, and scheduled tasks. This is the production instance — changes here affect live workflows.
Location
Container: LXC CT460 (hermes)
Tailscale IP:100.118.5.51 (⚠ 100.96.100.82 is the PVE hypervisorpve, not CT460 — corrected 2026-10-26)
Hostname:hermes
Ports: 9119 (gateway/API), 8085 (webhook) — ⚠ the old 8082 claim was dead: no 8082 listener on CT460 as of 2026-10-26
Memory: 14GB (upgraded from 5096MB on 2026-08-07)
Current State
Status: Active
Hermes version:v0.22.3 (2026.9.24), local 5b147ab036d6 — updated 2026-10-21 22:47→22:57 AWST; verified live 2026-10-26. (hermes update --check reports stable v0.22.5 available)
Python: managed runtime 3.14 (legacy venv/ on 3.11.15)
Default provider:custom:omni-101 → http://100.78.63.20:20128 (OmniRoute node omniroute-1, CT101/m93p) — verified live 2026-10-26. The custom:omni provider key does not exist in custom_providers, but 2 cron jobs still pin it (see systems/scheduled-tasks)
Fallback providers (live chain, re-verified 2026-10-26): nous / meituan/longcat-2.5-preview:free → opencode-zen / deepseek-v4.1-flash → custom:guacano / deepseek-v4.1-flash → custom:litellm / kilo-reflection-beam-free → kilocode / poolside/laguna-m.1:free → custom (http://litellm:4000/v1) / or-inclusionai_ling-2_6_1t. ⚠ The first entry is the dead nous credential — a fallover tries it first
Auxiliary models: all eight auxiliary: slots (approval, compression, curator, mcp, profile_describer, skills_hub, title_generation, vision) are no-think/freeapi/auto on custom:omni-101 with a freeapi/deepseek-v4-flash → kg/kilo-auto/free fallback chain (moved 2026-10-25 19:13)
Mattermost is currently unreachable — the gateway logs mattermost connect timed out after 30s, next retry in 300s (re-probed live 2026-10-26) and the Mattermost host does not answer: CT255 is stopped on pve and its Tailscale peer has been offline 36d. Treat Mattermost delivery as down until probed.