cavemem start fails with spawn EFTYPE on Windows

[Fundryi]

When it refers to "I" it means Claude did :,)

Fresh global install on Windows. Install + cavemem status work. cavemem start fails:

cavemem start
cavemem error: spawn EFTYPE
Same error via cmd /c cavemem start and node dist/index.js start — not the shim. Hooks also never auto-start the worker (same error on every hook spawn).

Setup:
Windows 10 (native, no WSL)
Node v23.11.0
cavemem 0.1.3 (global npm)

Cause:
Worker spawn does spawn(resolveCliPath(), ["worker", "run"], ...) where resolveCliPath() returns the raw .js path. Windows CreateProcess can't exec .js directly (no shebang honoring) → EFTYPE. Three call sites in dist/index.js do this. Linux/macOS unaffected.

Suggested fix: spawn with process.execPath + script path, or pass { shell: true } on win32.
Possibly related to #3 both are Windows spawn/bundle issues.

[BhoiDanny]

Im also getting the same bug or error.

Bug: EFTYPE error on cavemem start after path update

I am running this on my Windows setup and changed the paths in my .claude/settings.json to use forward slashes (/) instead of backslashes.

The hooks are working perfectly now after changing to the forward slashes and node before the path, but running cavemem start still throws an EFTYPE error.

Here is my config for context:

{
   "hooks": {
         "PostToolUse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "node C:/Users/.../AppData/Local/nvm/v25.9.0/node_modules/cavemem/dist/index.js hook run post-tool-use --ide claude-code"
          }
        ]
      }
    ], 
   ...
    },
 "mcpServers": {
    "cavemem": {
      "command": "node",
      "args": [
        "C:/Users/.../AppData/Local/nvm/v25.9.0/node_modules/cavemem/dist/index.js",
        "mcp"
      ]
    }
}

claude logs

cavemem status

[Sean-Powell]

I have also been getting the same on cavemem viewer