jared
/
cc-os
1
0
Fork 0
Code Issues 18 Pull Requests Packages Projects Releases Wiki Activity
cc-os/openspec/changes/archive/2026-06-09-memsearch-episod.../tasks.md

1.5 KiB
Raw Blame History

1. Install Plugin

  • 1.1 Run /plugin marketplace add zilliztech/memsearch in a Claude Code session
  • 1.2 Run /plugin install memsearch to activate the plugin
  • 1.3 Confirm the plugin is listed as active (no error messages)

2. Audit and Configure

  • 2.1 Run memsearch config list and record the actual defaults (especially memory_dir and milvus_db paths)
  • 2.2 If memory_dir is project-local, set memory_dir = "~/.memsearch/memory/" in ~/.memsearch/config.toml
  • 2.3 Re-run memsearch config list to confirm memory_dir resolves to a global path

3. Verify Stop Hook

  • 3.1 Check ~/.claude/settings.json (or plugin config) to confirm the memsearch Stop hook is registered
  • 3.2 Run a short test session (a few turns) and exit
  • 3.3 Confirm ~/.memsearch/memory/YYYY-MM-DD.md exists with content from the test session

4. Audit Built-in Guidance

  • 4.1 Review what memsearch adds to Claude's context (system prompt / tool definitions)
  • 4.2 Run a test query: memsearch search "what were we working on in the test session?"
  • 4.3 Assess whether built-in guidance handles cross-project episodic recall without conflicting with memory-vault/memory-project
  • 4.4 If routing gaps are found, author a minimal memory-search skill; otherwise skip

5. Mark Complete

  • 5.1 Update docs/memory-system/04-build-plan.md — mark Step 4 complete
  • 5.2 Update CLAUDE.md — add memsearch to Implemented Components, update design paragraph