About
Memory Health
Corpus-ops dashboard for the persistent agent memory corpus: counts by type, repo, and tool; stale-note detection; a credential-pattern policy scanner; and vector-based near-duplicate detection.
What it does
Corpus-ops dashboard for the persistent agent memory corpus: counts by type, repo, and tool; stale-note detection; a credential-pattern policy scanner; and vector-based near-duplicate detection.
Why it matters
- Keeps the agent memory corpus auditable as it grows across repos and tools.
- Surfaces stale notes so outdated guidance can be retired before it misleads an agent.
- Flags credential-like content so secrets never linger in searchable memory.
- Finds near-duplicate notes so the corpus stays lean and recall stays sharp.
Who uses it
Workspace ownersAdmins curating agent memoryTeams running multi-repo agents
Surface map
These controls, tabs, and related views are covered by this documentation set.
OverviewStalenessPolicyDuplicates
How it fits together
flowchart TD
U[Owner or admin] --> P[MemoryHealth.tsx]
P --> C[lib/memoryHealth.ts client]
C --> R[/api/portal/memory routes/]
R --> H[handlers/memory.php]
H --> G{owner or admin?}
G -- no --> X[403 denied]
G -- yes --> K[memCorpusId: bnl-memory corpus]
K --> M[(client_documents MySQL)]
H -. dedup only .-> Q[ClientRagPipeline + Qdrant vectors]