Claude-mem Plugin Issues on Windows (v8.5.9)
Environment: Windows 11, Claude Code v2.0.76
Issue 1: Worker Process Instability
The worker daemon fails to stay alive. It starts successfully but dies within seconds/minutes, causing all subsequent hooks to fail. Logs show:
Worker starts on port 37777
Worker dies (no error logged)
Next hook tries to start worker → "Worker failed to start. Is port 37777 in use?" or "Worker failed to start (health check timeout)"
Worker PID in worker.pid file constantly changes as new workers spawn
Issue 2: Summary Hook Failures
The Stop hook (summary-hook.js) fails with "fetch failed" because the worker isn't running when the hook fires. This means:
User prompts ARE captured (UserPromptSubmit hook works)
Assistant responses are NOT captured (Stop hook fails)
Observations are NOT processed into the database
Issue 3: Console Window Popups
Every hook execution spawns visible console windows (cmd.exe flashing) despite:
Adding Windows Defender exclusions for .claude-mem, .bun, .local, .claude\plugins
The windowsHide flag apparently not working on Windows 11
Evidence from Logs
[2026-01-06 09:46:57.445] [INFO ] [HOOK] → Stop: Requesting summary {workerPort=37777}
[2026-01-06 09:46:57.455] [ERROR] [HOOK] summary-hook failed fetch failed
[2026-01-06 10:07:22.556] [ERROR] [HOOK] summary-hook failed fetch failed
[2026-01-06 09:43:33.357] [ERROR] [SYSTEM] ✗ Worker failed to start Failed to start server. Is port 37777 in use?
Expected Behavior
According to changelog, v9.0.0 should fix these with "Windows PowerShell variable escaping in hook execution" and "Improved IPC detection for Windows managed mode" - but /plugin update did not pull v9.0.0.
Claude-mem Plugin Issues on Windows (v8.5.9)
Environment: Windows 11, Claude Code v2.0.76
Issue 1: Worker Process Instability
The worker daemon fails to stay alive. It starts successfully but dies within seconds/minutes, causing all subsequent hooks to fail. Logs show:
Worker starts on port 37777
Worker dies (no error logged)
Next hook tries to start worker → "Worker failed to start. Is port 37777 in use?" or "Worker failed to start (health check timeout)"
Worker PID in worker.pid file constantly changes as new workers spawn
Issue 2: Summary Hook Failures
The Stop hook (summary-hook.js) fails with "fetch failed" because the worker isn't running when the hook fires. This means:
User prompts ARE captured (UserPromptSubmit hook works)
Assistant responses are NOT captured (Stop hook fails)
Observations are NOT processed into the database
Issue 3: Console Window Popups
Every hook execution spawns visible console windows (cmd.exe flashing) despite:
Adding Windows Defender exclusions for .claude-mem, .bun, .local, .claude\plugins
The windowsHide flag apparently not working on Windows 11
Evidence from Logs
[2026-01-06 09:46:57.445] [INFO ] [HOOK] → Stop: Requesting summary {workerPort=37777}
[2026-01-06 09:46:57.455] [ERROR] [HOOK] summary-hook failed fetch failed
[2026-01-06 10:07:22.556] [ERROR] [HOOK] summary-hook failed fetch failed
[2026-01-06 09:43:33.357] [ERROR] [SYSTEM] ✗ Worker failed to start Failed to start server. Is port 37777 in use?
Expected Behavior
According to changelog, v9.0.0 should fix these with "Windows PowerShell variable escaping in hook execution" and "Improved IPC detection for Windows managed mode" - but /plugin update did not pull v9.0.0.