Is your Claude Code memory plugin burning more tokens than your actual work? For me, I measured it and it was using more than it was helping. The most popular option uses AI to compress every tool call. That compression fires hundreds of API calls per session, can eat up to 35GB of RAM via ChromaDB, and spawns a background HTTP server that causes database locks. Does memory actually need AI? For most developer workflows, the answer is no. When I want to know what I changed in the auth middleware last Tuesday, I need the raw file edits, not an LLM’s summary. So I built claude-recall:
- Zero API token cost (raw storage, no AI compression)
- Zero background daemons (direct SQLite writes)
- Zero data leaving your machine (auto-redaction of secrets)
- Full-fidelity session recovery (verbatim prompts, complete responses, every tool call)
- Date-aware search (“what did we deploy last Thursday?”)
- Cross-project search across every repo you’ve worked on
- One dependency. One SQLite file. 50MB typical database. Install in two commands: claude plugin marketplace add askqai/claude-recall claude plugin install claude-recall@claude-recall Apache 2.0. Contributions welcome. (no commercial benefit for me - I built it for myself and see if this could be helpful to anybody else) See the repo readme for common use cases and syntax. Let me know if you have feedback, next is adding a UI so you can see the history yourself easily. submitted by /u/Frequent-Suspect5758
Originally posted by u/Frequent-Suspect5758 on r/ClaudeCode
You must log in or # to comment.