claude-mem-lite
Eliminates context loss across Claude sessions, reducing rework and decision replay.
Persistent long-term memory for Claude Code via MCP — captures coding decisions, bugfixes, and context across sessions. Hybrid FTS5 + TF-IDF search with episode batching. Single SQLite DB, no external services. Alternative to claude-mem with 600x lower cost.
- Ask Claude to recall previous bug fixes and coding patterns from past development sessions automatically.
- Generate searchable memory of architectural decisions to maintain consistency across multiple coding projects.
- Automate capture of debugging context and solutions to prevent repeating the same troubleshooting work.
Eliminates context loss across Claude sessions, reducing rework and decision replay. SQLite-based approach cuts infrastructure costs while preserving institutional knowledge of code patterns and fixes.
Engineering teams using Claude for iterative development who need searchable session history without external dependencies.
https://github.com/sdsrss/claude-mem-lite
By sdsrss
How to Get It
claude plugins install sdsrss/claude-mem-lite
Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.
Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.
After installing, paste this into Claude:
Recall previous bug fixes and coding patterns from past development sessions automatically
Trust Signals Auto-scanned
Community Pulse New
No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.
Reviewer notes
Auto-scanned review. These are observations, not a security certification.
Scored from trust signals (evidence-eval-v1): 46 GitHub stars; contributors unknown; last commit 0d ago; license MIT.
Things to check
- Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.
- Single maintainer. Consider the risk if this person stops maintaining the project.
How to evaluate tools before deploying →
Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.
Evaluation
Scored from trust signals (evidence-eval-v1): 46 GitHub stars; contributors unknown; last commit 0d ago; license MIT.