You know that feeling when you open Claude and say “continue yesterday’s auth refactor” and it’s like “what refactor?” Yeah. Every. Single. Day. Claude has memory features but they’re honestly not great for real work. CLAUDE.md has a 200-line loading limit. Session management requires manually tracking session IDs and forking conversations. For long-term knowledge across projects, it’s pretty clunky. So I built memsearch - a Claude Code plugin that gives it actual persistent memory. Design philosophy is super simple: 4 shell hooks that run automatically (SessionStart, UserPromptSubmit, Stop, SessionEnd) 1 background watch process All memories stored in Markdown files (human-readable, git-friendly) Milvus vector index is just a cache (can rebuild anytime) Every time you submit a prompt, it auto-searches relevant memories and injects top-3 results into context. Claude doesn’t need to decide whether to search - it just gets the context automatically. No MCP server overhead, no context window bloat from tool definitions. Just pure text injection. Each session gets summarized using Haiku (async, super cheap) and appended to today’s .md file. Want to know what the AI remembers? Just open .memsearch/memory/2026-02-12.md and read it. Installation is stupid easy: /plugin marketplace add zilliztech/memsearch /plugin install memsearch Restart Claude and you’re done. Is it as feature-rich as claude-mem (the popular Node.js solution)? Nope. But that’s kinda the point. Sometimes you don’t need a full-stack memory system with Web UI and complex integrations. You just want Claude to remember stuff. Lightweight isn’t a compromise. It’s a philosophy. GitHub: https://zilliztech.github.io/memsearch/claude-plugin/ Would love feedback from folks who’ve dealt with Claude’s memory limitations! submitted by /u/jael_m
Originally posted by u/jael_m on r/ClaudeCode
You must log in or # to comment.