Auto-generated issue for claude-mem by `npm run bug-report`

claude-mem-generated-issue.md

Generate bug report? (y/n): y

🤖 Generating bug report with Claude... ✓ Issue formatted successfully

──────────────────────────────────────────────────────────── 📋 BUG REPORT GENERATED ────────────────────────────────────────────────────────────

Plugin causes 8+ bash processes and 1-minute UI freeze on startup

Problem Statement

The claude-mem plugin makes Claude Code completely unresponsive for approximately 1 minute during startup, spawning 8-9 bash/bun processes that block UI interactions. Typed commands are ignored or severely delayed until these processes converge. Force-terminating these processes immediately restores responsiveness, indicating the issue is caused by poorly implemented plugin hooks.

A detailed technical analysis of the implementation issues has been documented at: https://gist.github.com/futuremotiondev/a5cc12881828ec5caa031579f9691254

Environment

• Claude-mem: 12.3.8
• Claude Code: 2.1.116
• Node.js: v25.9.0
• Bun: 1.3.12
• OS: Microsoft Windows [Version 10.0.26200.8246] (x64)
• Platform: win32
• Plugin Path: ~\.claude\plugins\marketplaces\thedotmack
• Data Directory: ~\.claude-mem
• Dev Mode: No

Worker Status at Time of Report

• Running: Yes
• PID: 36284
• Port: 37777
• Uptime: 36 minutes
• Active Sessions: 0
• SSE Clients: 0

Database

• Path: ~\.claude-mem\claude-mem.db
• Size: 228.00 KB

Configuration

{
  "CLAUDE_MEM_MODEL": "claude-sonnet-4-6",
  "CLAUDE_MEM_WORKER_PORT": 37777,
  "CLAUDE_MEM_WORKER_HOST": "127.0.0.1",
  "CLAUDE_MEM_LOG_LEVEL": "INFO",
  "CLAUDE_MEM_CONTEXT_OBSERVATIONS": 50
}

Steps to Reproduce

1. Install the plugin: /plugin marketplace add thedotmack/claude-mem
2. Activate the plugin: /plugin install claude-mem
3. Restart Claude Code in a development/project directory
4. Observe that Claude Code becomes unresponsive and does not accept commands for approximately 1 minute
5. Check Task Manager/Process Explorer to see 8+ bash.exe and bun.exe processes spawned by the plugin
6. (Optional) Force terminate all bash and bun processes at once - Claude Code immediately becomes responsive again

Expected Behavior

• Claude Code should remain responsive during and after plugin initialization
• Plugin hooks should not spawn multiple redundant processes
• Startup time should not be significantly impacted by the plugin
• UI should accept user input immediately after Claude Code launches

Actual Behavior

• Claude Code UI freezes for ~60 seconds on startup when plugin is enabled
• 8-9 bash/bun processes are spawned simultaneously during activation
• User input (typed commands) is completely ignored or severely delayed during this period
• Killing the spawned processes immediately restores normal functionality
• The plugin's hook implementation appears to be causing cascading process spawns

Additional Context

The issue appears to be related to how the plugin's hooks are implemented. The processes eventually converge to a stable state after ~1 minute, but this makes the plugin unusable in its current form. A comprehensive technical analysis of the hook implementation issues has been provided in the linked gist above.

This issue makes the plugin completely unusable for daily work, as the startup delay and UI freeze prevent any productive use of Claude Code with the plugin enabled.

──────────────────────────────────────────────────────────── Suggested labels: bug, needs-triage Report saved to: C:\Users\futur\bug-report-2026-04-21-041501.md ────────────────────────────────────────────────────────────

🌐 Opening GitHub issue form in your browser... ❌ Failed to open browser. Please visit: