Alex Newman
9a9b00c6d8
- Built search-server.mjs successfully (55KB)
- Configured with packages: 'external' to use node_modules dependencies
- MCP config points to ${CLAUDE_PLUGIN_ROOT}/scripts/search-server.mjs
- Ready for deployment to plugin directory
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
Chroma MCP Experiment
This directory contains experimental scripts to test semantic search via ChromaDB without modifying production code.
Files
- chroma-sync-experiment.ts - Syncs SQLite observations/summaries to ChromaDB via Chroma MCP tools
- chroma-search-test.ts - Compares semantic search (Chroma) vs keyword search (FTS5)
- RESULTS.md - Document findings and make decision on production integration
Prerequisites
- Chroma MCP server configured in Claude settings
- Running:
uvx chroma-mcp --client-type persistent --data-dir ~/.claude-mem/vector-db
Running the Experiment
Step 1: Sync Data
npx tsx experiment/chroma-sync-experiment.ts
This will:
- Connect to your Chroma MCP server
- Create collection
cm__claude-mem - Sync all observations and sessions from SQLite
- Report sync statistics
Step 2: Test Search
npx tsx experiment/chroma-search-test.ts
This will:
- Run 8 test queries (4 semantic, 4 keyword)
- Compare Chroma semantic search vs FTS5 keyword search
- Display results side-by-side
Step 3: Document Results
Edit RESULTS.md with your findings:
- Which queries worked better with semantic search?
- Which worked better with keyword search?
- Is hybrid search worth the complexity?
Decision Point
Based on results:
- If semantic search provides significant value: Design production integration
- If FTS5 is sufficient: Keep current implementation, document why
Note
This is a pure experiment - no production code changes. All scripts are self-contained in this directory.