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.
4.9 KiB
title, type, status, created, updated, verified_on, confidence, tags, sources
| title | type | status | created | updated | verified_on | confidence | tags | sources | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Mnemosyne Vector Recall Ran FTS-Only | incident | resolved | 2026-10-04 | 2026-10-26 | 2026-10-26 | high |
|
|
Mnemosyne Vector Recall Ran FTS-Only
Summary
Until 2026-10-03, mnemosyne_recall was scoring keyword-only. fastembed was missing from every UV-managed runtime, so the dense (vector) leg of recall contributed no candidates. Nothing errored — recall still returned results, just worse ones. Detected and repaired 2026-10-03; re-verified live 2026-10-04.
Impact
- Semantic similarity search silently degraded to keyword/
FTS5matching. - No user-visible error, no failed cron job, no alert. The failure mode of a missing embedding backend is quiet recall degradation, not a crash — which is why it survived unnoticed.
- Nothing was lost: the residue is un-embedded rows, not missing rows (26 working / 6 episodic as of 2026-10-04). New writes embed normally.
Root Cause
Three overlapping conditions:
fastembedabsent from the managed runtimes. The gateway runs from a uv-managed venv under~/.hermes/installs/<install>/environments/<hash>/venv, and none of them hadfastembed. The legacy/home/hermes/.hermes/hermes-agent/venvhad it (0.8.0), which is why CLI-side checks looked healthy while the gateway could not embed.FASTEMBED_CACHE_PATHunset in~/.hermes/.env, so the local model directory was resolved implicitly rather than pinned.- Isolated-mode launches. The embedding worker can be launched with
python -I, which ignoresPYTHONPATH/PYTHONHOME— any path-based injection of the dependency does not survive that launch mode.
Fix (2026-10-03)
- Installed
fastembed(0.8.1) into the runtime the bootstrap actually selects. - Pinned
FASTEMBED_CACHE_PATH(models cached under~/.hermes/cache/fastembed,BAAI/bge-small-en-v1.5). - Extended
~/.hermes/scripts/hermes-runtime-deps-guard.sh— run every 15 min bymnemosyne-watchdog.py— so it now asserts, in the bootstrap-selected venv:fastembedimportable,FASTEMBED_CACHE_PATHset, and the model directory present, on top of its existingdotenv+mnemosynechecks in the installer python and every managed venv. - No gateway restart required.
Verification (live, 2026-10-04)
Memories with embeddings: 1759 / 2194 (80.2%)
Working memory: 726 / 752 (96.5%)
Episodic memory: 1033 / 1039 (99.4%)
vec_episodes_rowids: 1035
vec_working_rowids: 739
Embeddings generated (24h): 13 (working: 7, episodic: 6)
onnxruntime threads now appear in ~/.hermes/logs/mcp-stderr.log on each model load — direct evidence the embedding model is executing inside the gateway runtime. The dependency guard exits 0.
Caveat — do not misread mnemosyne doctor
mnemosyne doctor and the recall CLI run under the legacy venv/ (Python 3.11), where the sqlite_vec extension is not importable. Doctor therefore prints vec0: present_but_unloadable and marks the working/episodic vector tiers unavailable, even while the gateway embeds normally. The managed Python 3.14 venvs cannot import sqlite_vec either when probed directly. Judge vector health with ~/.hermes/scripts/check_embedding_coverage.py, not with doctor's vec0 line.
Benign noise
[E:onnxruntime:Default, env.cc:228 ThreadMain] pthread_setaffinity_np failed for thread: … mask: {0,} — a container CPU-affinity warning emitted on every model load. Not an error; do not chase it.
Current state (re-verified 2026-10-26)
The 2026-10-03 follow-up is satisfied: fastembed 0.8.1 is importable in both managed runtimes (19da945341ad4794ac2bc8ff9fdd3643, d41b16c8b6674454a4a819bd4acced1f) as well as 0.8.0 in the legacy venv, and FASTEMBED_CACHE_PATH is pinned in ~/.hermes/.env.
Current check_embedding_coverage.py output:
Memories with embeddings: 1899 / 2350 (80.8%)
Working memory: 815 / 842 (96.8%)
Episodic memory: 1084 / 1090 (99.4%)
vec_episodes_rowids: 1086
vec_working_rowids: 828
Embeddings generated (24h): 15 (working: 9, episodic: 6)
Both tiers are above the 95 % working-coverage reindex threshold, so the 6-hourly
monitor job b63ed5817212 (last_status: ok) has nothing to fire on. The 2026-10-04
figures below are superseded.
Follow-ups
- Confirm the embedding-coverage alert job (
b63ed5817212, every 6h, Telegram topic 102) still fires when working coverage drops below 95%. - Consider asserting
fastembedin all managed runtimes, not only the bootstrap-selected one, so a runtime switch cannot reintroduce this.