Healthy memory stores need periodic maintenance.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/xantorres/engram/llms.txt
Use this file to discover all available pages before exploring further.
doctor scans every promoted memory and surfaces four categories of concern: entries that have passed their decay horizon (stale), entries whose confidence has dropped below the useful threshold (low_confidence), entries that came from automated sources but have never been human-verified (unverified), and pairs of entries whose facts directly contradict each other (conflicts). No changes are made — doctor is a read-only diagnostic tool. Use the IDs it reports as input to promote, reject, or forget to resolve issues. version is the companion one-liner that confirms which release you are running.
doctor
Scans all promoted memories and prints a categorized report of entries that need attention. The command is entirely read-only: it will never modify, delete, or re-route any memory. Think of it as lint for your memory store.
Arguments & Options
This command takes no arguments or options.Report categories
| Category | Condition |
|---|---|
stale | The memory’s last-confirmed timestamp has passed its decay horizon. |
low_confidence | The memory’s confidence score is below 0.5. |
unverified | learned_by is harvest or imported and last_verified is None. |
conflicts | Two promoted memories that the dedup engine scores as contradictory. |
Output format
Each category is printed as a header with a count, followed by the affected IDs. Conflicts are listed as pairs:0 are still printed for completeness.
Example
Resolving findings
Each category maps to a recommended resolution: stale — Review withengram show <id>. If still accurate, re-promote with engram promote <id> --confirm to reset the decay clock. If outdated, engram forget <id>.
low_confidence — Investigate with engram show <id>. If the fact is reliable, re-stage it with a higher --confidence using engram remember. Otherwise engram forget <id>.
unverified — Run engram show <id> to read the harvested or imported content, then either confirm it with engram promote <id> --confirm (which sets last_verified) or discard it with engram reject <id>.
conflicts — Run engram show on both IDs to compare them. Decide which fact is authoritative, engram forget the outdated one, and optionally engram promote <id> --confirm the surviving one to refresh its timestamp.
doctor does not auto-fix anything. Every remediation step requires an explicit command. This is intentional — automated mutation of promoted memories without review would undermine the audit trail that makes Engram trustworthy.