Skip to content

v0.1.4 — Windows transcript discovery fix

Choose a tag to compare

@TheSylvester TheSylvester released this 31 May 15:10

Fixes

  • discovery: transcript discovery built its glob patterns with path.join, which emits backslashes on Windows. The glob library treats \ as an escape character, so C:\Users\…\.claude\projects\**\*.jsonl matched nothingbackfill and the steady-state mtime-scan found 0 transcripts on Windows-native, even though install, GPU/CUDA staging, and the Stop hook all looked healthy. Fixed with a shared transcriptGlob() helper that joins segments with / and normalizes any backslashes the root carries (the same normalization the Stop hook already applies to transcript_path). Real-time Stop-hook ingestion was unaffected; only the bulk discovery paths were broken.

Verified end-to-end on Windows-native (RTX 2060): 289 messages discovered (was 0), 245 embedded on GPU via flash-attention (-fa -ngl 999), semantic search returns results. WSL/Linux/macOS unaffected.

CUDA backend asset is byte-identical to v0.1.0–v0.1.3 (llama.cpp b5300).