30 lines
1.6 KiB
Markdown
30 lines
1.6 KiB
Markdown
|
## Why
|
||
|
|
|
||
|
|
The memory system has two layers — episodic ("what happened, when") and semantic/knowledge ("how do we…"). The semantic layer is live (Obsidian vault + Graphify). The episodic layer is missing: there is no way to answer "what were we working on last Tuesday?" or "did we discuss X recently?" across projects. memsearch is the purpose-built tool for this and fills that gap with zero custom code.
|
||
|
|
|
||
|
|
## What Changes
|
||
|
|
|
||
|
|
- Install memsearch as a global Claude Code plugin via the marketplace
|
||
|
|
- Confirm `memory_dir` is set to a global path (`~/.memsearch/memory/`) so all projects share one episodic store
|
||
|
|
- Verify the memsearch Stop hook is registering per-turn Q&A summaries correctly
|
||
|
|
- Audit memsearch's built-in Claude guidance after install before adding anything custom
|
||
|
|
|
||
|
|
## Capabilities
|
||
|
|
|
||
|
|
### New Capabilities
|
||
|
|
|
||
|
|
- `memsearch-episodic`: Episodic memory layer — install memsearch plugin, confirm global memory_dir, verify Stop hook produces daily memory files, and audit built-in guidance for routing gaps
|
||
|
|
|
||
|
|
### Modified Capabilities
|
||
|
|
|
||
|
|
_(none — existing hooks and skills are unchanged; memsearch ships with its own Stop hook)_
|
||
|
|
|
||
|
|
## Impact
|
||
|
|
|
||
|
|
- New tool available in all Claude Code sessions: `memsearch search "<query>"`
|
||
|
|
- memsearch Stop hook fires after every response turn (ships with plugin; no custom code)
|
||
|
|
- `~/.memsearch/memory/YYYY-MM-DD.md` daily files accumulate across all projects
|
||
|
|
- `~/.memsearch/milvus.db` is the persistent vector store (Milvus Lite, local)
|
||
|
|
- No changes to `session-end.sh`, `memory-vault`, `memory-project`, or Graphify
|
||
|
|
- A `memory-search` skill is conditional: only warranted if built-in guidance proves insufficient after install
|