claude-mem-lite

Based on the available evidence, this is best treated as an early open-source add-on rather than a broadly validated memory layer. The only source is the official GitHub repository summary, which supports its positioning, technical direction, and intended use, but does not prove real-world adoption, reliability, or measurable productivity gains. There is almost no heat proof and very limited usability proof, so the adoption judgment should stay conservative.

In practical terms, it is not training-grade long-term memory for Claude, and it is not a standalone knowledge base or team documentation platform. A more accurate analogy is a local persistent working-memory layer attached to Claude Code. The repo text says it stores coding decisions, bug fixes, and project context across sessions through MCP, and uses a lightweight SQLite search stack with FTS5 + TF-IDF. That makes it easier to resume ongoing development work without repeatedly re-explaining prior context.

On cost and setup, the evidence only supports that it is open source and mentions a lightweight SQLite-based stack.