Menu
Diagnoses Mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, or to verify the plugin is working correctly.
Searches and injects relevant memories into context before starting work on a task or topic. Use when beginning a new task, switching context, or when past decisions, preferences, or knowledge need to be loaded.
Consolidates stored memories by merging duplicates, resolving contradictions, and pruning stale entries. Use when memory count is high, search results feel noisy or repetitive, or periodic cleanup is needed to maintain memory quality.
Deletes memories by search query or memory ID with confirmation before removal. Use when removing outdated information, incorrect memories, sensitive data, or cleaning up after experiments.
Pins or unpins a memory to protect it from pruning during dream consolidation. Use when a memory is critical and must never be removed, such as core preferences, important decisions, or immutable personal facts.
Stores a memory verbatim from user input with appropriate category classification. Use when the user says remember this, save this, store this, note that, or explicitly asks to record a preference, decision, goal, or lesson.
Searches memories and displays compact one-liner results, or looks up a specific memory by ID. Use for quick memory lookups, checking if something was recorded, resolving [mem0:id] citations, or browsing memories without full category detail.
| name | status |
| description | Diagnoses Mem0 connectivity, API key validity, and memory read/write functionality. Use when memory operations fail, searches return empty, or to verify the plugin is working correctly. |
Run a diagnostic check on the Mem0 plugin. Useful for troubleshooting.
Run ALL checks, then display a single summary. Do not stop on the first failure.
Verify the API key is configured. The plugin loads it from MEM0_API_KEY env var or ~/.pi/agent/mem0-config.json.
...Report the resolved identity:
user_id: from config, env, or system userproject_id: auto-detected from current directorysession_id: current session identifierPASS if user_id and project_id are non-empty. WARN if any falls back to defaults.
Use mem0_memory tool with action="search", query="health check".
Use mem0_memory tool with action="add", content="Health check probe — safe to delete.".
## mem0 health
PASS API Key m0-dVe...
PASS Identity user=kartik, project=my-app, session=abc123
PASS Connectivity 142ms
PASS Write/Read write + delete OK
All checks passed.
If any check fails, add a ## Troubleshooting section with specific fix steps.
When invoked with --deep (e.g., /mem0-status --deep), run the standard checks above plus a memory quality scan.
Fetch all memories with mem0_memory action="get_all". Compare pairs within the same category for high textual overlap (shared nouns > 60%). Report:
Potential duplicates: <N> pairs
[mem0:<id1>] ~ [mem0:<id2>] — both about "<shared topic>"
Flag memories older than 180 days that haven't been accessed recently.
Within each category, flag pairs that assert opposing facts.
## Memory Quality
Duplicates: <N> · Stale: <N> · Contradictions: <N>
If all counts are 0: Memory quality: clean.
If any non-zero: append Run /mem0-dream to fix.