Jun 20, 2026 · 2:15 PM CDTHealthy but noisyjob c127dee776c7

Hermes memory health

Systems are functional; highest leverage is memory hygiene and recall quality.

Owner read

Mnemosyne is retired; LCM is the context engine of record. The highest-leverage work is LCM hygiene: keep sensitive-pattern redaction clean and make summaries preserve outcomes instead of tool-call noise.

100
Reliability score
78
Recall value score
47
Memory hygiene score
100
Context safety score

Mnemosyne

Retired. This audit is LCM-only; the Mnemosyne DB is frozen (last write 2026-05-19) and its cron jobs are paused.

LCM context health

DB / FTSok / ok
Messages23,676 (+0)
Summaries / ratio59 / 79.23
Externalized payloads646 · 17.5 MB
Sensitive raw hits0 (-2)

Hygiene

LCM hygiene

Oversized inline rows29
Data URI/base64 rows40
Redacted placeholder rows229
Lifecycle rows684
Sensitive redaction enabledtrue
Dynamic chunking enabledtrue

Healthy signals

  • Mnemosyne DB integrity passes
  • LCM DB integrity passes
  • LCM FTS indexes are in sync
  • LCM sensitive-pattern scan is clean
  • Mnemosyne source guards are installed
  • Mnemosyne compression model: ollama-cloud/gemini-3-flash-preview
  • Mnemosyne episodic prompt-echo scan is clean
  • Mnemosyne raw turn sync is disabled; explicit memories remain available

Warnings

Fix now

  • No fix-now items.

Watch

  • Raw transcript-shaped memories remain
  • High-importance memories have never been recalled
  • LCM lifecycle fragmentation is present but usually cosmetic

Distributions

LCM message roles

tool11,347
assistant10,823
user1,502
session_meta4

Recommended action

Highest leverageKeep LCM safety checks green: sensitive-pattern scan at zero, FTS in sync, externalization enabled. Treat lifecycle fragmentation as informational unless it accelerates day-over-day.

Cron delivery

NameDaily Mnemosyne + LCM memory audit page
Statusactive
Schedule0 9 * * *
Next run2026-06-21T09:00:00-05:00
Publisheshttps://agents.huntsyea.com/memory-audit/