// Memory providers
Memory providers
Mem0 and Pinecone are free/core advisory integrations. External memory can help recall context, but it never outranks current code, tests, or evidence.
// advisory only
Memory does not become truth
Mem0 and Pinecone can report provider status and support optional workflows, but .knowledge keeps them advisory.
External memory can suggest context. The trust layer still requires code, tests, and evidence before reviewers rely on it.
- Mem0 OSS: local/live adapter path with explicit health checks
- Pinecone: optional vector provider status and configuration boundary
- Graphiti and Zep: reserved outside the free/core release scope
Mem0 adapter
Mem0 health, dry-run, live adapter, and diagnostics.
Provider CLI
Offline provider status and install receipt behavior.
// live health
Mem0 live health uses bounded Python discovery
The Mem0 live health check can auto-detect Python from explicit flags, environment variables, active virtual environments, Windows Python launcher output, and common install locations.
It does not scan the full disk, install Python, install Mem0, or make network calls. On Windows, the first import mem0 can be noticeably slower than later imports, so live health uses a longer 30000 ms default timeout.
node .knowledge/tools/memory-mem0.js health --adapter live --json - Live Mem0 health
- Runs the explicit live health path with bounded Python discovery.
node .knowledge/tools/memory-mem0.js health --adapter live --python C:\Path\To\python.exe --json - Override Python
- Use this when Python is installed but not visible in PATH.
// technical notes