v10.0.8

thedotmack/claude-memv10.0.8Feb 16, 2026by thedotmack

AI Summary

This is a bug fix release addressing three critical issues: preventing orphaned Claude subprocesses from accumulating by adding explicit cleanup after SDK query loops, fixing Chroma binary resolution using absolute paths with fallback, and switching to WASM-based Chroma embeddings to eliminate native binary compilation issues across platforms.

Key Highlights

Added explicit subprocess cleanup using ProcessRegistry to prevent orphaned Claude subprocesses from accumulating (fixes #1010, #1089, #1090, #1068)
Replaced npx chroma run with absolute binary path resolution via require.resolve, falling back to npx with explicit cwd
Removed @chroma-core/default-embed dependency to eliminate native binary compilation issues on many platforms
Switched to WASM backend for Chroma embeddings, resolving cross-platform compatibility issues

Breaking Changes

Removed @chroma-core/default-embed dependency - applications relying on this will need to use the WASM-based embedding approach instead

Full Release Notes

## Bug Fixes

### Orphaned Subprocess Cleanup
- Add explicit subprocess cleanup after SDK query loop using existing `ProcessRegistry` infrastructure (`getProcessBySession` + `ensureProcessExit`), preventing orphaned Claude subprocesses from accumulating
- Closes #1010, #1089, #1090, #1068

### Chroma Binary Resolution
- Replace `npx chroma run` with absolute binary path resolution via `require.resolve`, falling back to `npx` with explicit `cwd` when the binary isn't found directly
- Closes #1120

### Cross-Platform Embedding Fix
- Remove `@chroma-core/default-embed` which pulled in `onnxruntime` + `sharp` native binaries that fail on many platforms
- Use WASM backend for Chroma embeddings, eliminating native binary compilation issues
- Closes #1104, #1105, #1110