Memory Diagnose
Run both retrieval diagnosis and config check, then give a combined verdict.
Steps
- Call
memory_retrieval_diagnose_oc(passtop_nif user specified, default 20) - Call
memory_config_doctor_oc - Combine both reports into a single diagnostic verdict
Output structure
Start with a one-sentence diagnosis, then present findings:
Retrieval quality is degraded. ~18% of entries are high-frequency low-quality false positives, likely FTS literal matches. Recommend: clean up low-quality entries first, then check embedding config.
Then show the two raw reports.
Suggesting next steps
- High false-positive rate → suggest
/memory-cleanup - Config problems found (minScore too low, no embedding provider) → highlight the specific config recommendations from the report
- Ambiguous entries in the "fuzzy zone" → mention that
memory_longterm_audit_oc(use_llm=True)can do semantic review
Notes
No API key required. Read-only — never modifies any files.