Files
agent-estate-wiki/systems/memory-backend.md
T
Tony0410 4126093644 stocktake(2026-10-26): correct 8 stale pages against live state — 0 stale remaining
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.
2026-10-26 04:27:49 +08:00

2.8 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
Memory Backend system active 2026-07-22 2026-10-26 2026-10-26 high
memory
mnemosyne
agent
raw/configs/hermes-config-sanitized.txt

Memory Backend

Purpose

Persist and recall agent memory across sessions.

Current Configuration

  • Primary backend: Mnemosyne (local native)
  • Memory enabled: true
  • User profile enabled: true
  • Memory char limit: 5000
  • User char limit: 3000
  • Flush every: 6 turns
  • Auto sleep: true
  • Default scope: session
  • Vector type: int8
  • Profile isolation: true (configured; requires gateway restart for the current messaging runtime)
  • Shared surface: data/shared/mnemosyne.db
  • Shared surface read: true
  • Sync roles: user
  • Skip contexts: cron, flush, subagent, background, skill_loop
  • Reflect max calls per session: 3 (reflect.disabled_for_cron: true)
  • Sleep threshold: 50 turns
  • Nudge interval: 10
  • Ignore patterns: none set
  • Live totals (2026-10-26): 2,350 memories — 842 working / 1,090 episodic / 418 memoria_facts

Storage Location

  • Mnemosyne home: ~/.hermes/mnemosyne/
  • DB: ~/.hermes/mnemosyne/data/
  • Backups: ~/.hermes/mnemosyne/backups/
  • Logs: ~/.hermes/mnemosyne/logs/
  • Models: ~/.hermes/mnemosyne/models/
  • Config: ~/.hermes/mnemosyne/config.yaml

Known Issues

  • Health monitoring currently treats capture as stale only after 24 hours; an activity-aware comparison is preferable to catch dry-intake failures sooner without false alarms during idle periods.
  • The 2026-08-01 automatic-capture failure and repair are documented in incidents/2026-08-01-mnemosyne-capture-failure.
  • Vector recall degraded silently until 2026-10-03 — fastembed was missing from every uv-managed runtime, so mnemosyne_recall fell back to FTS5 keyword scoring with no error raised. Repaired 2026-10-03; the 15-min dependency guard now asserts fastembed and the model cache path. See incidents/2026-10-03-mnemosyne-vector-recall-fts-only.
  • Embedding coverage re-verified 2026-10-26 — check_embedding_coverage.py reports 1,899 / 2,350 (80.8 %) embedded; working 815 / 842 (96.8 %) and episodic 1,084 / 1,090 (99.4 %). Both tiers are above the 95 % reindex threshold, so no reindex was triggered. fastembed 0.8.1 is present in both managed runtimes and 0.8.0 in the legacy venv; FASTEMBED_CACHE_PATH is pinned. The 2026-10-03 follow-up (assert fastembed in all managed runtimes) is now satisfied.

Correction (2026-07-22, per Anthony): this page previously referenced Hindsight as a possibly-used backend on this box. That was a mix-up with a different Hermes instance — see comparisons/memory-backends.