ROOT CAUSE FIXED - systems/skills-index.md had TWO WRITERS: the repo wiki-maintain.sh (302 skills / 68 categories) and the stale ~/.hermes/scripts/wiki-maintain.sh (mtime 2026-08-17, 349 skills / 26 categories - it used Path.rglob() and counted the parked .archive/ tree) were different scripts with different generators, and wiki-maintenance/SKILL.md line 569 pointed the 23:59 nightly audit at the stale path while the 03:00 stocktake ran the repo path. Each job overwrote the other's page; neither raised an error. The stale copy is now a delegating wrapper with no generator logic, and the repo script gained --no-build so the wrapper honours the old interface without a second generator. Verified by execution. Live-probe corrections: - infrastructure/docker-services.md: CT200 61 running / 68 total (was 62); worldmonitor-seeder-scheduled does not exist on ANY host (zero 'seeder' matches across CT200/201/333/460); CT333 first container renamed again (nostalgic_leavitt -> flamboyant_mahavira); CT201 20/26, CT460 1/1, CT1001 1/9. - infrastructure/tailscale.md: node table verified programmatically - 52 rows vs 52 live IPv4 peers, no live peer missing, no orphan row, every online/offline state matching. conduit 59d->60d, ubuntu-server-xfce 75d->76d. Serve table still matches tailscale serve status exactly. - infrastructure/hosts.md: skills figure corrected to 302 / 68 categories. - index.md: skills-index bullet refreshed to the 2026-11-05 figures. New incident: incidents/2026-11-05-skills-index-generator-divergence.md (closes the still-open item on the 2026-08-15 skills-index drift incident). Freshness: 0 stale / 123 fresh / 3 no-date of 126 pages.
6.1 KiB
6.1 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | ||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Known Hosts and Paths | infrastructure | partial | 2026-07-22 | 2026-11-05 | 2026-11-05 | medium |
|
Known Hosts and Paths
Verified Hosts
| Host | Role | Address | Verified |
|---|---|---|---|
| localhost (this host) | Primary Hermes runtime, Xvfb, file storage | :99 display (Xvfb :99 -screen 0 1600x1200x24) |
Yes (live probe 2026-10-26) |
| litellm | LiteLLM proxy | http://litellm:4000/v1 |
Yes (from config) |
custom:Omniroute:20128 |
OmniRoute proxy (CT600 node omniroute) |
http://omniroute:20128/v1 → 100.88.81.19:20128 |
Yes (live probe 2026-10-26: 6,480 models) |
custom:omni-101 |
OmniRoute proxy (CT101 node omniroute-1) — the live default provider |
http://100.78.63.20:20128 |
Yes (live probe 2026-10-26) |
| CT201 | Runtipi, Homepage dashboard | 100.96.244.39 (Tailscale), 192.168.178.77 (LAN) |
Yes (live probe 2026-10-30 — LAN address corrected from 192.168.178.166) |
| CT460 | Hermes host, Camoufox, cua-driver | hermes.kangaroo-eel.ts.net, 100.118.5.51 (Tailscale) |
Yes |
PVE pve |
Proxmox VE hypervisor hosting CT460 and the other pve guests |
100.96.100.82 (Tailscale), pve.kangaroo-eel.ts.net |
Yes (live pct list 2026-10-26) |
PVE m93p |
Second, unclustered Proxmox VE 9.2.10 hypervisor | 100.104.51.98 (Tailscale) |
Yes (live pct list 2026-10-26) |
| CT450 (hermesagent) | Hermes Agent v0.22.5 (2026.9.24), local bf0203a794a0 — same build as CT460; hermes-webui, hermes-ui (Vite). ⚠ a stale root-level /usr/local/bin/hermes on CT450 still reports v0.19.0 — the live agent is the hermes-user install under ~/.hermes/hermes-agent |
100.98.205.112 (Tailscale), 192.168.178.65 (LAN) |
Yes (live probe 2026-10-30 — version corrected from v0.22.3, build from 5b147ab036d6 to bf0203a794a0) |
Project Paths
| Path | Type | Notes |
|---|---|---|
/home/hermes |
Hermes home | ~/.hermes/ contains config, skills, cache |
/home/hermes/workspace |
Workspace | default terminal cwd |
/home/hermes/.local/bin/hermes |
Hermes binary | |
/home/hermes/.hermes/config.yaml |
Config | _config_version: 51 |
/home/hermes/.hermes/skills/ |
Skills dir | 302 skills across 68 categories (.archive/ excluded — 46 archived; re-verified 2026-11-05) |
/home/hermes/.hermes/cron/ |
Cron jobs | 29 jobs — 26 enabled / 3 disabled (re-verified 2026-10-31 00:3x). ⚠ Superseded: the 2026-10-30 03:3x reading was 25 / 4 — the 4th disabled job, ea79a2107e36 Mnemosyne Health Monitor, was auto-paused 2026-10-30 01:04 after a gateway-connection failure, but that pause lasted only until 10:02:48, when its long-running slot closed completed, incident ea79a2_d93c3acdc4f2 auto-closed resolved, and the job returned to enabled: true / last_status: ok / streak 0. CT460 itself was then dark for 5 h 30 m on 2026-10-30 (PVE pve rebooted; host boot 16:24:00, CT460 16:28:00, scheduler resumed 16:37:21 — ≈39 cron slots lost, 0 failures) → incidents/2026-10-30-ct460-host-outage-scheduler-gap |
/home/hermes/.hermes/mnemosyne/ |
Mnemosyne DB | backups/, data/, logs/, models/ |
/home/hermes/.cua-driver/packages/releases/0.9.0-x86_64-unknown-linux-gnu/cua-driver |
cua-driver | v0.9.0 |
~/.camofox/ |
Camofox profiles | managed persistence |
~/.camoufox/ |
Camoufox profiles | multiple profiles present |
/home/hermes/.hermes/browser_screenshots/ |
Browser captures | |
/home/hermes/workspace/agent-estate-wiki/ |
Wiki — authoring tree (source of truth, pushed to Gitea) | |
/home/hermes/wiki/agent-estate-wiki/ |
Wiki — Obsidian/Quartz vault mirror (local-only git; synced per audit, never pushed) | |
/home/hermes/obsidian-vault/ |
Obsidian vault | personal notes (50 - Research etc.) |
/home/hermes/hermes-webui/ |
Hermes WebUI | web UI source |
/home/hermes/hermes-ui/ |
Hermes Desktop browser (Vite dev) | present on CT460 and CT450 port 5174 |
/home/hermes/camofox-browser/ |
Camofox browser | |
/home/hermes/camoufox/ |
Camoufox source | |
/home/hermes/services/ |
Services dir | |
/home/hermes/www/ |
Web root | |
/home/hermes/go/ |
Go workspace | |
/home/hermes/Downloads/ |
Downloads |
Compose Files (Docker runtime state unknown)
/home/hermes/.hermes/hermes-agent/docker-compose.yml/home/hermes/hermes-webui/docker-compose.yml/home/hermes/workspace/readlater/docker-compose.yml
Homelab References
- PVE host
pve:pve.kangaroo-eel.ts.net(100.96.100.82) — verified via livepct list2026-10-26 (17 LXCs) - PVE host
m93p: 100.104.51.98, Proxmox VE 9.2.10 — verified via livepct list2026-10-26 (19 LXCs). Guest IDs collide between the two hosts - CT600 (
omniroute): OmniRoute server,100.88.81.19— running and live;omnirouteis the hostname that resolves to it - CT601 (
omni): the old CT601 OmniRoute guest no longer exists on either hypervisor (pct config 601→ no such config on bothpveandm93p). The orphanedomniTailscale peer (100.93.204.4) has since expired out of the tailnet entirely — as of the 2026-10-30 live probe the tailnet contains no peer namedomniand no peer at100.93.204.4, so the old "offline 69d" description no longer applies. The only OmniRoute nodes left are CT600 (omniroute) and CT101 (omniroute-1). - CT101 (
omniroute, m93p): second OmniRoute node,100.78.63.20— running
Unverified
- Individual LXCs are verified only when probed directly; the two
pct listsnapshots above are the current authority for what is running - Guests not present in those
pct listoutputs are not running on either hypervisor — do not assume existence from older session notes
Note (2026-10-29): CT201 no longer hosts the Steel Browser — the containers, images, network, project dir and Tailscale Serve routes were all removed when Steel was deleted from the estate. CT333's separate, orphaned Steel copy was removed at the same time. → comparisons/steel-vs-camoufox