memsearch
v0.4.17Automatic semantic memory for Claude Code — remembers what you worked on across sessions
2.4kupdated 1 week ago
Source
git clone https://github.com/zilliztech/memsearchClone the source, then follow the repository's marketplace instructions for your runtime. The plugin root is plugins/claude-code/ inside the repository.
Layout
├── .claude-plugin/plugin.json├── skills/memory-config/SKILL.md├── skills/memory-recall/SKILL.md└── skills/memory-to-skill/SKILL.md
Skills3
Diagnose and configure MemSearch memory behavior for the Claude Code plugin. Use when the user asks about MemSearch configuration, plugin summarization, PROJECT.md/USER.md maintenance, memory directories, index health, provider routing, prompt files, or migration/compatibility questions.
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this before'. Also use when you see `[memsearch] Memory available` hints injected via SessionStart or UserPromptSubmit. Typical flow: search for 3-5 chunks, expand the most relevant, optionally deep-drill into original transcripts via the anchor format. Skip when the question is purely about current code state (use Read/Grep), ephemeral (today's task only), or the user has explicitly asked to ignore memory.
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under .memsearch/skill-candidates/, not Claude Code's own skills system.
Manifests1
{
"name": "memsearch",
"version": "0.4.17",
"description": "Automatic semantic memory for Claude Code — remembers what you worked on across sessions"
}