18 KiB
Anthony's Systems Wiki
Operational knowledge for Anthony's agents, infrastructure, model routing and automation. Last updated: 2026-10-24
⚠ Two Proxmox hosts exist — always qualify a guest with its host. A second unclustered hypervisor,
m93p(100.104.51.98, PVE 9.2.0), was discovered during the 2026-10-14 stocktake. Guest IDs collide between the two hosts.
Start here
- current-state — Current systems status
- systems/hermes-agent — Hermes Agent overview and version
- systems/current-profile — Active Hermes profile details
Systems
Core
- systems/hermes-agent — Agent version, install, config paths
- systems/current-profile — Active profile details
- systems/nextcloud — Nextcloud file sharing (CT270)
- systems/guanaco — Guanaco LLM proxy on CT205 (Ollama stack)
- systems/model-providers — LiteLLM + OmniRoute providers, routing setup
- systems/memory-backend — Mnemosyne vector memory, settings
- systems/mnemosyne — Mnemosyne cron jobs and config evidence
- systems/omniroute — OmniRoute catalog, combos, and host path
- systems/openrouter — OpenRouter current state and history
- systems/opencode-go — OpenCode Go subscription, model limits, pricing
- systems/nanobot — Nanobot current state and history
- systems/browser-backend — Camofox (primary,
systemd --useron CT460, REST:9377) + Steel (disabled); memory-containment drop-in and the 2026-10-12 ceiling event documented - systems/hermes-ui — Browser Hermes Desktop (przbadu/hermes-ui)
- systems/paseo — Paseo coding-agent daemon + web terminal workspace (CT460, :6767)
- systems/ignis — Ignis browser-native Obsidian (wiki interface)
- systems/terminal-backend — Shell persistence, working directory
- systems/tool-search — Always-on lazy discovery for external tools
Integrations
- systems/conduit — Conduit: Hermes on Anthony's phone (dashboard plugin + iOS app — voice calls, cards, push). Plugin tree
~/.hermes/plugins/conduit_push, v0.64.0(HEADeaa14be), upstreamkaishi00/hermes-conduit-notifier; gateway on:9119; one registered device (iPhone app2.0.0). Carries an uncommitted in-tree patch — the memory-start timeout fix below. - systems/messaging-integrations — Telegram, Discord, email, Slack, etc. Mattermost's long-running red now has a cause: CT255 is stopped (peer offline 29d; host answers neither
:8065nor ICMP). - systems/push-notifications — Cadu/Vory push bridge (
hermes-push,vory-push): gateway on:9119, state in~/.hermes/push/. Broken —connected: false(the bridge dials a name that resolves to127.0.1.1where nothing serves 443); chronic, not a blip. - systems/scheduled-tasks — As of 2026-10-24 00:2x: 28 jobs (25 enabled, 3 disabled), 4 non-clean
last_status, and 2026-10-23 closed 169 / 0 — the third zero-failure day in four. The 2026-10-09 provider timeout storm is now fully closed:1b23c042e17dran clean on its 10-23 08:04 slot, closing the storm's last two rows, so all 12 are closed and unclosed incident rows fell 4 → 2. ⚠ New off-cron fault, fixed in-window: Conduit voice calls were being abandoned by the memory layer — the plugin hard-coded a 10 s budget for a request that includes Mnemosyne's 10–45 s cold start; three calls ran without recall. Patched to 60 s (CONDUIT_MEMORY_TIMEOUT_S) + degraded-not-aborted onTokenError; dashboard restarted 18:54:43, no abort since. Patch uncommitted → incidents/2026-10-22-conduit-memory-start-timeout, systems/conduit. The 10-22 stocktake overrun did not repeat (10-23 03:07 committed250c735). Prior window: As of 2026-10-22 00:1x: 28 jobs (25 enabled, 3 disabled), 9 non-cleanlast_status, and 2026-10-21 closed 171 / 1 — where the single failure is a failure mode this wiki had not seen.dca8482e4f76(Daily Marketing Job Radar) died at 07:40:48 after 40 m 36 s onRuntimeError: Service temporarily unavailable: all targets were skipped by pre-dispatch filters reset after 19m 20s→ incidents/2026-10-21-omniroute-pre-dispatch-filter-skip.08eb86f02d37cleared (08:30 slot clean; incident resolved 08:37:21) and 2026-10-20 settled at 169 / 0 + 1unknown. ⚠ Hermes Agent was updated to0.22.3at 22:47 → 22:57 with its pre-update snapshotskipped→ systems/hermes-agent. Prior window: 2026-10-20 closed 168 / 0 — the first zero-failure day since 10-12. Theomni-101503 fault did not recur (back tomonitoring) and 4 incident rows closed → 9 unclosed. ⚠ Two new findings: the Gitea config backup has not pushed since 2026-08-08 (75 unpushed commits) while its row readsok→ incidents/2026-08-08-gitea-config-backup-push-dead; and a gateway unclean exit on 2026-10-20 orphaned a digest run — no delivery row, no incident → incidents/2026-10-20-gateway-unclean-exit-orphaned-run. Also: the global model default moved tonousdirect (meituan/longcat-2.5-preview:free) on 2026-10-20, taking the 8 unpinned jobs off OmniRoute while 20 of 28 still pin it → systems/current-profile. Prior window: 28 cron jobs (25 enabled, 3 disabled); 12 carry a non-cleanlast_statusas of 2026-10-20 00:09 — up from 7, because theomniroute-1503 resource-pressure fault returned on 2026-10-19 (second burst in four days: 9 model calls across 8 jobs, 06:01 and 07:01 → 12:01, allmodel: smart-routeoncustom:omni-101, while/api/healthstayed200 ok) → incidents/2026-10-16-omniroute-503-resource-pressure. 2026-10-19 closed 159 / 13 against 10-18's 168 / 1. The Mosquito Tracker was removed (29 → 28 jobs), and the 2026-10-18 degenerate-stream placeholder-delivery mode remains an open question → incidents/2026-10-18-degenerate-stream-canned-substitute. Earlier: the connection-refused storm (2026-10-14 → 10-15) — 24 model-call failures across 12 jobs, ~34 h of digests blanked. All 18 model-calling jobs still sit oncustom:omni-101with no failover. - systems/skills-index — Installed skills inventory (306 skills / 70 categories as of the 2026-10-23 03:07 stocktake; regenerated daily by the 03:00 job). The generator now excludes
_archive/— the earlier 346/347 counts included it. Freshness at that run: 2 stale / 94 fresh / 6 no-date of 102 pages (freshness-20261023.txt). Note:SKILL.mdfiles on disk still exceed the index (the generator de-dups one nested duplicate; see systems/scheduled-tasks). ⚠ The 2026-10-22 slot ran 97 m 58 s (vs 16 m 01 s on 10-21), finishedcompletedwith deliverysuppressedand committed nothing; the 10-23 slot closed that hole.
Incidents
-
incidents/2026-10-22-conduit-memory-start-timeout — Conduit voice calls were silently running without memory, 2026-10-22 → 10-23. The phone plugin gave one request — including the Mnemosyne provider start — a hard-coded 10 s budget (
MEMORY_TIMEOUT_S), while Mnemosyne's cold start for aconduit-voicesession runs 10–45 s. Three calls were abandoned at the memory layer (Memory provider 'mnemosyne' start for Conduit timed out; abandoning the call: 10-22 11:28:17, 10-22 13:16:37, 10-23 18:29:16) and answered with no recall of prior conversation. Fixed 10-23 in the plugin's working tree: default 60 s (CONDUIT_MEMORY_TIMEOUT_Soverride) plus aTokenErrorguard that logs and proceeds without recall instead of aborting; dashboard restarted 18:54:43 and no abort line exists after it (two calls closed cleanly 00:03:23 / 00:06:57 on 10-24). The patch is uncommitted — a plugin update reverts it. The cold start itself was not optimised. → systems/conduit, systems/mnemosyne -
incidents/2026-10-21-omniroute-pre-dispatch-filter-skip — A third failure signature from the
custom:omni-101/smart-routepin, 2026-10-21. The Daily Marketing Job Radar (dca8482e4f76, 07:00 weekday) died at 07:40:48 after 40 m 36 s onRuntimeError: Service temporarily unavailable: all targets were skipped by pre-dispatch filters reset after 19m 20s— no 503, no connection error, no repetition loop, and zero 503 rows exist for that day (last 2026-10-19 09:02). Its 07:00 sibling85edf6772bcacompleted normally, so the node was serving; the run wrote no output (cron_incomplete_no_output, 82 msgs / 47 tool calls). Incidentdca848_014affeb6954was closed 2026-10-22 07:59:22 when the next daily slot ran clean. Not caused by the 22:47hermes update— that landed 15 h later. → systems/omniroute -
incidents/2026-10-20-gateway-unclean-exit-orphaned-run — The gateway exited uncleanly on 2026-10-20 (09:09:01,
suspected_oom=False) and orphaned a live cron run.08eb86f02d37(Gmail Action Digest, 08:30 slot) was claimed 08:31:03 and closedunknown— “Scheduler restarted after this execution's owner exited before a durable terminal state; whether side effects ran is unknown.” No delivery row exists for the slot and no incident row was created; the job table keeps showing the previous slot's 503. 20 unclean exits since 2026-08-01 (5 clustered on 2026-08-14/15); this one ended a 27-day clean run. Open: orphan-recovery on restart, and treating a delivery-targetedunknownas a probable non-delivery. -
incidents/2026-08-08-gitea-config-backup-push-dead — Green row, dead job, 2.5 months: the daily Hermes Config Backup to Gitea has not pushed since 2026-08-07 11:00:47.
e27da6c34bbbreadslast_status: okand its executions readcompletedevery night while 75 commits sit unpushed (fatal: could not read Username for 'https://gitea.kangaroo-eel.ts.net'— HTTPS remote, no credential, no helper). Telegram failure notices have fired daily (message_id 8447, 2026-10-20 11:00); AgentMail failed. No off-box~/.hermesbackup in 2.5 months. Second instance of the pattern after the GitHub Trending Radar token revocation. → infrastructure/backups -
incidents/2026-10-18-degenerate-stream-canned-substitute — The repetition-loop failure mode, 2026-10-18: the FreshRSS Midday run (
ecc1fc13655a) wrote "Your request was not processed…", delivered it to topic:346at 12:08:11, then died at 12:08:25 onRuntimeError: Model output entered a repetition loop and the stream was cut mid-loop. A delivered message is not evidence of delivered content — open question: should the guard suppress delivery / re-queue instead of substituting text on the job's normal route? Second surface (2026-10-20 18:37): an interactivedesktopsession received the same canned line afterRebuilt-message restart limit (3) exceeded→reason=rebuilt_restart_limit_exceeded … response_len=0, so the substitute is emitted by the harness's failure path generally, not only by the repetition-loop guard. The user's question in that session — Nous OAuth dashboard auth plus a gateway token — was never answered. -
incidents/2026-10-16-omniroute-503-resource-pressure —
omniroute-1load-sheds model calls withHTTP 503 … resource pressure— two bursts: 2026-10-16 → 10-17, and again 2026-10-19. Burst 1: 9 model calls across 7 jobs over ~19 h, self-cleared (reported then as10-17 = 162 / 5; the DB reads 163 / 5 — corrected 2026-10-20). Burst 2, 44 h later with an identical signature and blast radius: 9 model calls across 8 jobs on 2026-10-19 (06:01 + 07:01 → 12:01, whole day 159 / 13)./api/healthread200 okthroughout both. Status:active→ back tomonitoringon 2026-10-21 — 2026-10-20 ran 168 / 0 with zero rows carrying the resource-pressure string, so the second burst is over; it stays a standing risk until the single-node topology changes. 4 rows closed on 10-20 (dca848_867d9caa96a8,85edf6_256c5e150bc4,ecc1fc_c9976ea24553,ecc1fc_21a72aa11cc4); unclosed rows 13 → 9 (8alerted/ 1detected); the ledger still tags every 503 rowfailure_type: unknown, so triage on error text. Single-node topology still open — and every job that failed readsmodel: smart-route,provider: custom:omni-101. -
incidents/2026-10-14-omniroute-node-connection-refused-storm — Fleet-wide 34-hour cron blackout, 2026-10-14 → 10-15:
omniroute-1(100.78.63.20:20128, providercustom:omni-101) refused TCP connections, so every model-calling cron job failed on every slot — 24 genuine model-call failures across 12 jobs (+12 derivative watchdog reds), and all digests for ~34 h were silently suppressed. All 18 enabled model-calling jobs ride this one node with no failover. Recovered 10-15 22:01 (resolved) -
incidents/2026-10-09-cron-provider-timeout-storm — Fleet-wide provider timeout storm: 15 failed executions across 10 jobs on 2026-10-09, all
RuntimeError: Request timed out.on the aliases behindcustom:omni-101, 00:00 → 15:00 AWST. CLOSED — all 12 incident rows are now resolved; the last two (1b23c0_c35703f637b8,1b23c0_103cbe04a79b, both on the weekly Friday job1b23c042e17d) closed 2026-10-23 08:04 when that slot ran clean, and the job readsokagain -
incidents/2026-10-09-memory-recall-relevance — Recall relevance: a stale conversational episode outranked current-state facts on an open question; capture and vectorisation verified healthy, the ranking fix was never persisted in config (unresolved)
-
incidents/2026-10-05-dead-model-pin-repin — Seven cron jobs on dead model pins (
cliprox/terra,qwen3.5:397b,deepseek-v4-flash,gpt-5.6-terra) repinned to routing aliases oncustom:omni-101; failing set 7 → 0 (resolved 2026-10-05) -
incidents/2026-10-03-mnemosyne-vector-recall-fts-only — Mnemosyne recall had been scoring keyword-only (fastembed missing from the managed runtimes); repaired 2026-10-03, coverage re-verified at 96.5% working / 99.4% episodic
-
incidents/2026-10-03-ct450-hermes-update — Chaos instance CT450 updated v0.19.0 → v0.21.5 (resolved); access path and pre-flight checks documented
-
incidents/2026-10-01-cliproxy-connection-auth-expired — OmniRoute
cliprox/terraconnection credential expired (all 3 jobs on the pin failed, settled 2026-10-04); closed 2026-10-05 when all three were repinned off the pin -
incidents/2026-08-26-work-outlook-basic-auth-disabled — Work Outlook mailbox unreachable: tenant allows only
XOAuth2, himalaya configured for password (open since 2026-08-26) -
incidents/2026-09-28-hermes-managed-runtime-deps — Managed-runtime venvs missing
dotenv/mnemosynebroke every cron worker (resolved 2026-09-30); dependency guard now runs every 15 min. Recurred 2026-10-10 inside the gateway runtime env —mnemosyneandelevenlabsmissing from the committed uv env the gateway loads; both repaired and verified the same evening -
incidents/2026-08-18-mnemosyne-capture-pipeline — Mnemosyne capture pipeline broken (Aug 2026, superseded): capture verified healthy 2026-10-12 — 786 working rows, +2 that day, 98.3 % embedded
-
incidents/2026-08-15-skills-index-drift — Skills index 4x undercount (66 vs 330 installed); fixed via auto-regeneration
Monitoring & Dashboards
- systems/homepage-dashboard — Homepage dashboard (CT201)
- systems/home-assistant — Home Assistant integration
Reports
- reports/uber-eats/index — Uber Eats monthly spend reports
- reports/communities-wa-social-media-audit-2026 — Department of Communities WA social media audit and first-day brief
- systems/obsidian — Obsidian vault structure and conventions
- queries/retained-research-answers — Retained research answers (fastest VNC clients, 2026-10-11)
Infrastructure
Services
- infrastructure/hosts — Hosts, containers, important paths
- infrastructure/docker-services — Docker compose files
- infrastructure/credentials-map — Where credentials live (no values)
- infrastructure/network-map — Zones, hosts, and ports across LAN, Tailscale, and the public tunnel
- infrastructure/domains-and-tunnels — martinwa.org hostnames and Cloudflare Tunnel routing
- infrastructure/backups — hermes backup CLI, retention, and gaps
Networking
- infrastructure/proxmox — PVE hosts (two:
pve8.x +m93p9.2.0, unclustered, IDs collide), VMs, LXC containers, storage (/mnt/ssd088.17 % / ~63 GiB free, 2026-10-14) - infrastructure/tailscale — Tailscale serve routes (CT460 verified exactly) and the 48-node tailnet inventory (re-verified 2026-10-19:
guest-vps,openmausbot,openmausbot-vmadded;mattermostoffline 29d) - systems/cloudflare-tunnel — ct207-hosted tunnel serving Hermes publicly
Concepts
- concepts/agent-memory — Memory model
- concepts/model-routing — Routing concepts
- concepts/persistent-shells — Terminal persistence
- concepts/browser-automation — Browser automation concepts
- concepts/tool-calling — Tool calling patterns
Decisions
- decisions/index — Decision index
- decisions/keep-openrouter-as-fallback — Keep OpenRouter as fallback provider
- decisions/persistent-shell-enabled — Enable shell persistence
Comparisons
- comparisons/camoufox-vs-chrome — Camoufox vs Chrome
- comparisons/hermes-vs-nanobot — Hermes vs Nanobot
- comparisons/memory-backends — Memory backend comparison
- comparisons/model-routers — Model router comparison
Runbooks
- runbooks/multiplexer-setup — Multi-profile gateway multiplexer setup
- runbooks/diagnose-docker — Docker diagnosis
- runbooks/recover-docker-service — Docker service recovery
- runbooks/restart-hermes — Hermes restart procedure
- runbooks/restart-browser — Browser restart procedure
- runbooks/update-hermes-safely — Safe Hermes update
- runbooks/restore-openrouter — OpenRouter restoration
- runbooks/provider-health — Provider health check
- runbooks/troubleshoot-tool-loop — Tool loop troubleshooting
- runbooks/gateway-resource-resilience — Gateway resilience
- runbooks/job-radar — Job Radar search, Notion, dashboard and recovery procedure
Raw
- raw/configs/hermes-config-sanitized.txt — Sanitized config