Jun 26, 2026 · 9:00 AM CDTNeeds actionjob c127dee776c7

Hermes memory health

Core systems are running, but one or more reliability or safety checks need attention.

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
98
Recall value score
100
Memory hygiene score
50
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
Messages34,076 (+970)
Summaries / ratio118 / 66.33
Externalized payloads881 · 23.4 MB
Sensitive raw hits91 (+0)

Hygiene

LCM hygiene

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

Healthy signals

  • Mnemosyne DB integrity passes
  • LCM DB integrity passes
  • LCM FTS indexes are in sync
  • 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
  • LCM sensitive-pattern redaction is enabled

Warnings

Fix now

  • Raw sensitive-looking values remain in LCM

Watch

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

Distributions

LCM message roles

tool16,712
assistant14,826
user2,534
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-27T09:00:00-05:00
Publisheshttps://agents.huntsyea.com/memory-audit/