stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13) - skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299) - runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated - comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest - incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised - incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused) - 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists) - log.md addendum + index.md date bump; no page deleted, no secrets written
This commit is contained in:
@@ -3,8 +3,8 @@ title: Cloudflare Tunnel
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [system, network, cloudflare]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -33,6 +33,13 @@ Exposes internal homelab services, including Hermes, to the public internet with
|
||||
`hermes.martinwa.org` (9119), `hermes-chat.martinwa.org` (8787), `tg.hermes.martinwa.org` (19119)
|
||||
and `hermes-desktop.martinwa.org` (5174). Full live list in [[infrastructure/domains-and-tunnels]].
|
||||
|
||||
> **Ingress re-read live 2026-11-11 from `/etc/cloudflared/config.yml` on ct207 — unchanged.**
|
||||
> `cloudflared.service` is still **active**, the tunnel is still `ct207-tunnel`, and the four
|
||||
> Hermes-relevant entries are exactly as recorded: `hermes.martinwa.org`→`100.118.5.51:9119`,
|
||||
> `hermes-chat.martinwa.org`→`100.118.5.51:8787`, `tg.hermes.martinwa.org`→`100.118.5.51:19119`,
|
||||
> `hermes-desktop.martinwa.org`→`100.118.5.51:5174`. `mcp-portal.martinwa.org` is **still absent**
|
||||
> from the ingress list — the 2026-10-20 "unresolved" flag stands, now three weeks old.
|
||||
|
||||
## Connected systems
|
||||
- [[systems/hermes-agent]] — the service actually reached through this tunnel
|
||||
- [[infrastructure/domains-and-tunnels]] — full hostname table
|
||||
|
||||
+9
-2
@@ -3,8 +3,8 @@ title: Guanaco
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-08-14
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [llm, proxy, router, guanaco, ollama]
|
||||
sources: [live-probe, session-history]
|
||||
@@ -40,6 +40,13 @@ LLM proxy/router providing model routing and tool-call formatting for the Ollama
|
||||
### v0.8.11 (previous)
|
||||
- Had known DSML tag leakage issues where malformed tool-call output could leak raw `<dsml_...>` syntax into model context stream
|
||||
|
||||
> **Live probe 2026-11-11 — the v0.8.15 record holds.** `/root/.guanaco/repo` on CT205
|
||||
> (`pct exec 205`) still sits at tag **`v0.8.15`**, HEAD `5df435e3de11a51401972696d47daf9144b0d140`
|
||||
> (the abbreviated `5df435e` recorded above), and the Ollama API on `localhost:11434/api/version`
|
||||
> returns **200**. CT205 (`ollama`) is running; its LAN address is `192.168.178.158`.
|
||||
> Note a naming nuance this page does not carry: Hermes's `guacano` provider points at
|
||||
> **`http://ollama:11000/v1`**, i.e. Guanaco's own proxy port, not Ollama's `11434`.
|
||||
|
||||
## What DSML Is
|
||||
DSML = "Daily Smart Messaging Log" — Guanaco's tool-call formatting layer for the cmdcode client. When a model emits a tool call, Guanaco formats it through DSML. Malformed output from the model could previously leak raw tags (`<dsml_invoke>`, bare `>` characters) into the conversation context, which confused downstream models.
|
||||
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Headless Server
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [system, browser]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -39,6 +39,12 @@ still binds **all interfaces** — `0.0.0.0:5901` and `[::]:5901` — while both
|
||||
are correctly loopback-only (`127.0.0.1:6080`, `127.0.0.1:6081`).
|
||||
|
||||
|
||||
> **Re-verified 2026-11-11 via `ps aux` + `ss -ltnp` — the live chain is exactly as recorded.**
|
||||
> One `Xvfb :99` (`-screen 0 1600x1200x24 -ac -nolisten tcp`), one `x11vnc -display :99 …
|
||||
> -rfbport 5901 -nopw` bound to `0.0.0.0:5901`/`[::]:5901`, one `fluxbox`, and two `websockify`
|
||||
> instances (`127.0.0.1:6080`→`5900`, `127.0.0.1:6081`→`5901`). **Port 5900 still has no listener** —
|
||||
> the 6080 pair still points at a dead port. Camofox's own listener is separately live on `*:9377`.
|
||||
|
||||
## Connected systems
|
||||
- [[systems/hermes-agent]] (browser backend uses this display — see [[systems/browser-backend]] / [[comparisons/camoufox-vs-chrome]])
|
||||
- [[infrastructure/hosts]]
|
||||
|
||||
@@ -3,8 +3,8 @@ title: hermes-ui (Browser Hermes Desktop)
|
||||
type: system
|
||||
status: live
|
||||
created: 2026-07-30
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [hermes, webui, desktop, browser]
|
||||
---
|
||||
@@ -31,6 +31,12 @@ The official Hermes Desktop renderer, extracted from the `hermes-agent` monorepo
|
||||
> (the `/ui` Tailscale Serve route) — and **8787** is the Hermes WebUI (`python`, `0.0.0.0:8787`,
|
||||
> the `/webui` route). Don't conflate 5174 / 5175 / 8787.
|
||||
|
||||
> **Both deployments re-verified 2026-11-11.** CT460: `0.0.0.0:5174` held by a `node` process
|
||||
> (`ss -ltnp`), `/home/hermes/hermes-ui/` present. CT450: `ss -ltn` inside the container shows
|
||||
> `0.0.0.0:5174` and `/home/hermes/hermes-ui` exists. The 5175/8787 distinction still holds:
|
||||
> `127.0.0.1:5175` is a `python3` (the `/ui` Tailscale Serve route) and `0.0.0.0:8787` is the
|
||||
> Hermes WebUI (`python`).
|
||||
|
||||
## How It Works
|
||||
|
||||
- Runs as a Vite dev server, proxying REST/auth/WebSocket to a running Hermes gateway (`http://127.0.0.1:9119` by default).
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Nextcloud
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-08-17
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [nextcloud, file-sharing, self-hosted, infrastructure]
|
||||
sources: []
|
||||
@@ -40,6 +40,12 @@ Self-hosted file sync and sharing platform running on Proxmox LXC container.
|
||||
| news | 28.7.0 | active | RSS reader |
|
||||
| nextcloud_announcements | 5.0.0 | active | |
|
||||
|
||||
> **Re-verified 2026-11-11 — every fact on this page still holds.** CT270 (`nextcloud`) is running;
|
||||
> `occ status` reports **installed: true, version 33.0.2.2, maintenance: false,
|
||||
> needsDbUpgrade: false**; the container holds `192.168.178.56` (LAN) and `100.90.102.19`
|
||||
> (Tailscale); `occ` lives at `/var/www/nextcloud/occ`. The `ncdownloader` NC33 incompatibility is
|
||||
> unchanged and still the only app-level issue recorded.
|
||||
|
||||
## Known Issues
|
||||
- **ncdownloader v1.0.23 incompatible with Nextcloud 33 (2026-08-17):** App calls `OC\Server::getAppConfig()` which was removed in NC33. Crashes the `/settings/admin/overview` page with a fatal error. Fix: disable the app via `occ app:disable ncdownloader`. No data loss — ncdownloader settings preserved in DB, app just needs a compatible update.
|
||||
|
||||
|
||||
+7
-2
@@ -3,8 +3,8 @@ title: Obsidian Vault
|
||||
type: systems
|
||||
status: active
|
||||
created: 2026-07-26
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [obsidian, notes, vault, homelab]
|
||||
---
|
||||
@@ -35,6 +35,11 @@ Personal knowledge base — notes, research, projects, and agent documentation.
|
||||
> (`obsidian-livesync`) on the `m93p` host** (`/opt/obsidian-livesync/`, holds only a `.env`).
|
||||
> Full folder table, left for reference:
|
||||
|
||||
> **Re-verified 2026-11-11 — the 2026-10-20 correction still holds.** `/home/hermes/obsidian-vault/`
|
||||
> still contains only `50 - Research/` and `Cron Outputs/`, and is still **not** a git repo.
|
||||
> `/home/hermes/wiki` is still a **local-only** git repo (`git remote -v` empty) tracking the
|
||||
> `agent-estate-wiki/` mirror plus `reports/uber-eats/`. No numbered-folder vault exists on this box.
|
||||
|
||||
## Folder Structure
|
||||
| Folder | Purpose |
|
||||
|---|---|
|
||||
|
||||
@@ -3,8 +3,8 @@ title: OpenRouter
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: medium
|
||||
tags: [system, openrouter, provider]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -29,6 +29,10 @@ OmniRoute’s catalog includes provider names and model IDs consistent with Open
|
||||
> model catalog**, not as directly-routable Hermes providers. Routing to OpenRouter therefore still
|
||||
> goes through OmniRoute, exactly as recorded here.
|
||||
|
||||
> **Re-verified 2026-11-11.** `custom_providers` in `/home/hermes/.hermes/config.yaml` still holds
|
||||
> exactly five entries — `litellm`, `guacano`, `Omniroute:20128`, `command-code`, `omni-101` — with
|
||||
> **no `openrouter` entry**. The 2026-10-20 claim holds unchanged 22 days on.
|
||||
|
||||
## History
|
||||
- **User-provided:** Previously used; now largely replaced by LiteLLM and OmniRoute paths
|
||||
- **Verified:** Decision page `keep-openrouter-as-fallback` exists, indicating retain intent
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Installed Skills
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-11-10
|
||||
verified_on: 2026-11-10
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [skills, hermes]
|
||||
sources: []
|
||||
|
||||
@@ -3,8 +3,8 @@ title: Terminal Backend
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-22
|
||||
updated: 2026-10-20
|
||||
verified_on: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
verified_on: 2026-11-11
|
||||
confidence: high
|
||||
tags: [terminal, shell, backend, persistence]
|
||||
sources: [raw/configs/hermes-config-sanitized.txt]
|
||||
@@ -28,6 +28,13 @@ Live `terminal:` block re-read from `/home/hermes/.hermes/config.yaml` on 2026-1
|
||||
`container_persistent: true`, `docker_mount_cwd_to_workspace: false`, `docker_run_as_host_user: true`.
|
||||
`backend: local` and `persistent_shell: true` are unchanged since 2026-07-22.
|
||||
|
||||
> **Full `terminal:` block re-read 2026-11-11 — every value unchanged.** `backend: local`,
|
||||
> `persistent_shell: true`, `timeout: 180`, `home_mode: auto`, `container_cpu: 1`,
|
||||
> `lifetime_seconds: 300`, `container_memory: 5120`, `container_disk: 51200`,
|
||||
> `container_persistent: true`, `docker_mount_cwd_to_workspace: false`,
|
||||
> `docker_run_as_host_user: true`. One nomenclature correction: the working-directory key is spelled
|
||||
> **`cwd`** (`cwd: /home/hermes/workspace/`), not `workdir` — the value itself is unchanged.
|
||||
|
||||
## Persistence
|
||||
- Shell state (venv, env vars, aliases) persists across terminal calls
|
||||
- Working directory fixed to `/home/hermes/workspace`
|
||||
|
||||
@@ -3,9 +3,9 @@ title: Hermes Tool Search
|
||||
type: system
|
||||
status: active
|
||||
created: 2026-07-25
|
||||
updated: 2026-10-20
|
||||
updated: 2026-11-11
|
||||
review_after: 2026-11-20
|
||||
verified_on: 2026-10-20
|
||||
verified_on: 2026-11-11
|
||||
version_applies_to: Hermes Agent on CT460
|
||||
confidence: high
|
||||
tags: [hermes, automation, system]
|
||||
@@ -49,6 +49,11 @@ tools:
|
||||
request instead of waiting for the tool schemas to cross an automatic token
|
||||
threshold.
|
||||
|
||||
> **Config re-read 2026-11-11 — byte-for-byte unchanged.** `tools.tool_search` in
|
||||
> `~/.hermes/config.yaml` still reads `enabled: "on"`, `threshold_pct: 20`,
|
||||
> `search_default_limit: 8`, `max_search_limit: 50`, `listing_max_tokens: 8`. `tools:` carries no
|
||||
> other key. Tool Search was exercised throughout this stocktake session.
|
||||
|
||||
## Verified result
|
||||
|
||||
- 80 external tools were deferred in the production gateway.
|
||||
|
||||
Reference in New Issue
Block a user