Postgres data cluster by meaning (semantic search and visualization)
Database triggers keep embeddings in sync—no ETL pipelines or separate vector database needed.
Verbatim semantic memory across Claude Code sessions - pgvector + local Ollama embeddings
Pgvector + BM25 hybrid retrieval with honest LongMemEval benchmarks for Claude Code memory.
Developers using Claude Code who lose context between sessions
MemPalace · mem0 · letta
Database triggers keep embeddings in sync—no ETL pipelines or separate vector database needed.
Three-tier memory architecture solves context bloat for Claude Code and Copilot CLI users.
Valkey vector search for Claude Code memory—clever glue, narrow audience.
Runs extraction and search server-side so your local MCP is a tiny HTTP client — no local DBs, no giant RAM leaks, and an easy npx install and .mcp.json or global MCP registration. It exposes clear tools (save_memory, recall_memories, extract_memories, get_project_context) and adds project-scoped + global preferences — a pragmatic fix for Claude Code's tiny flat-file memory. The tradeoff is obvious: usefulness depends on the hosted API (privacy, uptime, cost), and the repo looks early-stage with minimal commits and docs beyond the quickstart.
Scatter-gather retrieval with prompt caching beats naive vector search for Claude Code memory.
Claude memory is solved—Pinecone, LLamaIndex, and Continue already do this.