Ran wiki-maintain.sh (skills-index regenerated: 302 skills / 69 categories, unchanged; freshness report 0 stale / 109 fresh / 3 no-date of 112 pages; Quartz rebuilt and deployed). Freshness is not accuracy. A live-vs-page diff found real drift on five pages. All corrections verified against live sources first. - infrastructure/tailscale: node table rebuilt from tailscale status --json. 50 non-funnel nodes (49 IPv4 peers + hermes), not 54. 2 IP changes, 4 peers expired out of the tailnet. Zero IP mismatches, zero missing/extra rows on re-verification. m93p records online (peer record chronically stale, third occurrence -- ping + SSH confirm). CT460 :443 route set (12 paths) and CT201 :443/:8443 tables re-probed and match. - systems/scheduled-tasks: fleet is 29 jobs (25 enabled / 4 disabled), not 28/25/3. Mnemosyne Health Monitor ea79a2107e36 was auto-paused 2026-10-30 01:04:22 after its 00:01:08 slot closed "unknown" on a gateway-connection failure. Non-clean last_status is 4, not 3. "Failing (delivery only)" is 2. Seven job rows carried stale error claims for jobs since cleared to ok -- each marked superseded with a dated correction, not rewritten (SCHEMA rule 9). - NEW incidents/2026-10-30-mnemosyne-health-monitor-paused: the job's own failure notice was never delivered (deliveries.db has zero rows for 2026-10-30), so the incident row is the only trace. Job not re-enabled and gateway not restarted by this run; root cause recorded as unverified. - infrastructure/hosts: CT201 LAN is 192.168.178.77 (was .166); CT450 Hermes is v0.22.5 / bf0203a794a0, same build as CT460 (page said v0.22.3 / 5b147ab036d6); cron count 29/25/4; orphaned "omni" peer has expired out of the tailnet entirely. Skills count of 302 left alone -- it is correct. - systems/homepage-dashboard: live app count is 123 (was 114); grid is a responsive repeat(auto-fill, minmax(230px, 1fr)), not a fixed 5-column grid; tab bar is built from the service groups (renderTabs iterates state.groups), so the settings.yaml layout block and its tab:/columns: keys are inert -- there is no "Overview" tab; saved theme is Boarding Pass / light, not dark amber; manager.py runs inside the homepage-manager container; and the "no Traefik container" evidence was wrong -- the container exists but is stopped (Exited (255) 2 months ago). The conclusion that Traefik does not occupy 443 stands. Same evidence error corrected in tailscale.md. Also corrected two of my own first-pass errors before committing: the homepage tab list (groups vs tabs) and the CT450 version (a stale root-level /usr/local/bin/hermes reports v0.19.0; the live agent is the hermes-user install at v0.22.5). No secrets written -- provider names, key names and HTTP status codes only.
5.5 KiB
5.5 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-10-30 | 2026-10-30 | 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 69 categories (.archive/ excluded) |
/home/hermes/.hermes/cron/ |
Cron jobs | 29 jobs — 25 enabled / 4 disabled (the 4th disabled job, ea79a2107e36 Mnemosyne Health Monitor, was auto-paused 2026-10-30 01:04 after a gateway-connection failure) |
/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