Files
agent-estate-wiki/comparisons/memory-backends.md
T
Hermes 341dda95dd 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
2026-11-11 03:52:48 +08:00

4.0 KiB

title, type, status, created, updated, verified_on, confidence, tags, sources
title type status created updated verified_on confidence tags sources
Memory Backends comparison active 2026-07-22 2026-11-11 2026-11-11 high
comparison
memory
raw/configs/hermes-config-sanitized.txt

Memory Backends

Purpose

Document Hermes's memory backend on this box, and record why the taxonomy this page assumed (Hindsight, Mnemosyne, file-backed) doesn't actually apply here.

Correction (2026-07-22, per Anthony)

This wiki previously stated Hindsight was this box's predecessor memory backend, based on archived hindsight-* script names found under ~/.hermes/scripts/ and a "Hindsight clean memory bank" mention in current-state.md. That was wrong — Hindsight has nothing to do with this Hermes box. It was confused with a different Hermes instance (most likely ct450 "hermesagent", the older/original Hermes install still running in this homelab — see infrastructure/domains-and-tunnels). All Hindsight-specific pages (systems/hindsight.md, decisions/use-hindsight-for-memory.md, runbooks/check-hindsight.md) have been deleted rather than left as deprecated stubs, since they describe something that was never true of this box.

The three archived scripts (hindsight-watchdog.py.archived, hindsight_migration_watchdog.py.archived, honcho_to_hindsight_import.py.archived) that had been sitting under ~/.hermes/scripts/ were removed on 2026-07-22 at Anthony's request, closing out the mix-up entirely.

What's actually true here

  • Only backend ever verified on this box: Mnemosyne — local native plugin (~/.hermes/plugins/mnemosyne), not a docker service. See systems/mnemosyne and systems/memory-backend for full config.
  • No evidence of a file-backed-only memory mode being used either — it's Mnemosyne or nothing on this install.

OpenViking evaluation (2026-08-12) — NOT adopted

  • Anthony explored OpenViking (Volcengine/ByteDance context database, filesystem-style knowledge hierarchy, tiered retrieval, 6-category auto extraction) as a potential memory provider.
  • Not adopted: memory.provider is single-slot — setting hermes config set memory.provider openviking would fully replace Mnemosyne, with no parallel/dual-active mode.
  • Risk assessment flagged: schema mismatch, embedding drift, scope leakage, provenance loss, and one-way/no-rollback migration with no dry-run snapshot.
  • Verdict: stay on Mnemosyne. Config verified memory.provider: mnemosyne (2026-08-12). No migration was performed.

Re-verified 2026-10-20 — Mnemosyne is still the only backend, and the OpenViking decision still holds. memory.provider: mnemosyne, memory_enabled: true, flush_min_turns: 6, memory_char_limit: 5000, user_char_limit: 3000, user_profile_enabled: true, nudge_interval: 10; Mnemosyne sub-block auto_sleep: true, default_scope: session, vector_type: int8, sleep_threshold: 50, profile_isolation: true, shared_surface_path: data/shared/mnemosyne.db, shared_surface_read: true. No openviking key anywhere in config.yaml. No migration performed.

New since 2026-08-12: mnemosyne.skip_contexts: [cron, flush, subagent, background, skill_loop] and reflect.disabled_for_cron: true — Mnemosyne capture is deliberately skipped in cron contexts, which is why scheduled jobs produce no working memories. See concepts/agent-memory and systems/mnemosyne.

Re-verified 2026-11-11 — still Mnemosyne only. memory.provider: mnemosyne, memory_enabled: true, flush_min_turns: 6, memory_char_limit: 5000, user_char_limit: 3000, nudge_interval: 10, user_profile_enabled: true; Mnemosyne sub-block auto_sleep: true, default_scope: session, vector_type: int8, sleep_threshold: 50, profile_isolation: true, shared_surface_path: data/shared/mnemosyne.db, shared_surface_read: true. No openviking key anywhere in config.yaml; no migration performed. The OpenViking NOT-adopted verdict stands.