Back to Claude Mem

๐ŸชŸ Windows folks โ€” we think we fixed the big one. Help us test?

plans/windows-testers-post.md

13.15.33.6 KB
Original Source

๐ŸชŸ Windows folks โ€” we think we fixed the big one. Help us test?

๐Ÿ› What was broken

  • ๐ŸงŸ Leftover programs. claude-mem starts a little search helper in the background. When it shut down, Windows only stopped the top program โ€” the helpers underneath kept running like zombies.
  • ๐Ÿ”’ Stuck port. Those zombies held onto the door claude-mem needs to start up again. So it couldn't restart. So every prompt got blocked. One person hit this 834 times in a single session.
  • ๐Ÿ’พ Disk eaten alive. The zombies also left junk files behind, forever. One user measured 144 GB of it. ๐Ÿ˜ณ
  • ๐Ÿคซ Search quietly dying. The helper could grab the wrong Python off your machine and just... stop working. No error. No warning. Memory search silently stopped.

๐Ÿ”ง What we fixed

  • ๐Ÿ‘จโ€๐Ÿ‘ฉโ€๐Ÿ‘งโ€๐Ÿ‘ฆ Shutdown now closes the whole family of programs, not just the parent.
  • ๐Ÿงน Stopped killing things mid-download, so junk files stop piling up.
  • ๐Ÿ The wrong Python can't sneak in anymore.
  • ๐ŸŽฏ Made sure we never shut down the wrong program by accident (this one took 7 rounds of review to get right ๐Ÿ˜…).
  • ๐Ÿค– Added real Windows tests. Our tests used to never actually start the search helper on Windows โ€” which is exactly why these bugs kept slipping through. Now they do, on every change.

โœ… Actually proven on Windows

Not "should work" โ€” these ran on a real Windows machine and passed:

  • โœ… Search helper starts, saves a memory, finds it again
  • โœ… Shutdown leaves zero leftover programs
  • โœ… Still works even with a messy Python setup

๐Ÿ“ฆ Want to try it? (~10 min)

You'll need: Node.js and Git. โ˜• Grab a coffee, the build takes a few minutes.

Open PowerShell and paste these one at a time:

powershell
git clone https://github.com/thedotmack/claude-mem.git
cd claude-mem
git checkout windows-megafix
npm install
npm run build-and-sync
node dist\npx-cli\index.js doctor

(That's every Windows fix rolled into one branch โ€” PR #3661.)

That last one prints a health check. ๐Ÿฉบ

๐Ÿ‘€ What "it worked" looks like

  • โœ… doctor shows green/OK lines โ€” especially Bun, uv, and Worker daemon
  • โœ… Claude Code starts normally, no blocked prompts
  • โœ… Memory search actually returns results
  • โœ… Stop claude-mem, then run Get-Process uv,python -ErrorAction SilentlyContinue โ€” you should see nothing left over. That's the whole fix in one command. ๐ŸŽ‰

๐Ÿ†˜ If something breaks

Drop us a comment with:

  1. ๐Ÿ“‹ The full output of node dist\npx-cli\index.js doctor
  2. ๐ŸชŸ Your Windows version
  3. ๐Ÿ“œ Your latest log file from %USERPROFILE%\.claude-mem\logs\

Genuinely โ€” a broken report is just as useful as a working one. That's the point of testing. ๐Ÿ™

โช Want out? Easy.

powershell
npx claude-mem@latest install

Puts you straight back on the normal released version. Nothing to undo, nothing to clean up. ๐Ÿ‘


๐Ÿ“š The pull requests, if you're curious

  • #3661 โ€” the rollup branch you just installed (windows-megafix), all of the below combined

  • #3644 โ€” the big one (leftover programs, stuck port, disk junk, silent search death)

  • #3647 โ€” code search silently returning nothing on Windows

  • #3648 โ€” data getting saved to the wrong folder if you used ~\ in your settings

  • #3649 โ€” you now get a clear message if Git Bash is missing, instead of a cryptic crash

  • #3657 โ€” fixes building from source on Windows (it needed a Mac/Linux-only tool before ๐Ÿ™ƒ)

โš ๏ธ These aren't merged yet โ€” you'd be testing a preview. That's exactly what we need right now. ๐Ÿ’›