Plugin hooks fail to start on Claude Code session initialization

Problem Statement

Claude-mem plugin hooks are failing to start when a new Claude Code session is initialized. The worker service, context hook, and user message hook all fail with "The operation was aborted" errors. This issue started occurring recently without any apparent configuration changes.

Since the issue started appearing, it takes an abnormally long time from entering claude in the terminal and the actual claude UI to appear.

Environment

• Claude-mem Version: 8.5.2
• Claude Code Version: 2.0.76
• Node.js: v24.11.0
• Bun: 1.3.4
• Operating System: Linux 6.6.87.2-microsoft-standard-WSL2 (x64)
• Platform: WSL2 (linux)
• Dev Mode: No

Paths:

• Plugin: ~/.claude/plugins/marketplaces/thedotmack
• Data Directory: ~/.claude-mem
• Database: ~/.claude-mem/claude-mem.db (23.24 MB)

Configuration:

• Model: claude-sonnet-4-5
• Worker Port: 37777
• Worker Host: 127.0.0.1
• Log Level: INFO
• Context Observations: 50

Steps to Reproduce

1. Open Claude Code in terminal
2. Observe startup errors during session initialization

Expected Behavior

Plugin hooks should start successfully without errors, allowing claude-mem to function normally during the Claude Code session.

Actual Behavior

Three plugin hooks fail to start with abort errors:

⎿ SessionStart:startup says: Plugin hook "bun "/home/vscode/.claude/plugins/cache/thedotmack/claude-mem/8.5.2/scripts/worker-service.cjs" start" failed to start: The operation was aborted.. Check that the command exists and is executable.

⎿ SessionStart:startup says: Plugin hook "node "/home/vscode/.claude/plugins/cache/thedotmack/claude-mem/8.5.2/scripts/context-hook.js"" failed to start: The operation was aborted.. Check that the command exists and is executable.

⎿ SessionStart:startup says: Plugin hook "node "/home/vscode/.claude/plugins/cache/thedotmack/claude-mem/8.5.2/scripts/user-message-hook.js"" failed to start: The operation was aborted.. Check that the command exists and is executable.

Additional Context

• The worker appears to be running despite the errors (PID: 7506, Uptime: 1 minute, 1 active session)
• Database exists and is accessible
• Settings file is present and configured
• Issue started recently without any known configuration changes
• Running in WSL2 environment with both Node.js and Bun installed