Multiple hook errors: UserPromptSubmit, PostToolUse (Bash, Edit, Grep, Read)

[dayakarreddyn]

Multiple hook errors: UserPromptSubmit, PostToolUse (Bash, Edit, Grep, Read)

Problem

Claude-mem is throwing multiple hook errors during operation, affecting various tool interactions including user prompts and post-tool-use hooks for Bash, Edit, Grep, and Read operations.

Environment

• Claude-mem Version: 9.0.12
• Claude Code Version: 2.1.29
• Node.js: v25.3.0
• Bun: 1.3.8
• Operating System: macOS 26.3 (arm64)
• Platform: darwin
• Dev Mode: No

Configuration Status

• Plugin Path: ~/.claude/plugins/marketplaces/thedotmack
• Data Directory: ~/.claude-mem
• Database Path: ~/.claude-mem/claude-mem.db
• Database Exists: ❌ No
• Settings File: ~/.claude-mem/settings.json
• Settings Exist: ❌ No
• Worker Running: ❌ No

Observed Behavior

The following hook errors are occurring:

UserPromptSubmit hook error
PostToolUse:Bash hook error
PostToolUse:Edit hook error
PostToolUse:Grep hook error
PostToolUse:Grep hook error
PostToolUse:Read hook error

Expected Behavior

Claude-mem should execute hooks without errors during normal operation. All tool use hooks should complete successfully.

Possible Causes

Based on the diagnostics:

1. Missing database: The database file (~/.claude-mem/claude-mem.db) does not exist
2. Missing configuration: Settings file (~/.claude-mem/settings.json) does not exist
3. Worker not running: The worker process is not active

These missing components may be preventing hooks from executing properly.

Additional Context

This appears to be either a fresh installation that hasn't been properly initialized, or a corrupted installation where critical files have been removed. The hook errors suggest that claude-mem is attempting to interact with the database or configuration files that don't exist.

[github-actions]

The GitHub issue reports multiple hook errors in the Claude-mem system, specifically during UserPromptSubmit and PostToolUse operations (Bash, Edit, Grep, and Read). The problem appears to stem from critical missing components, including the database file (claude-mem.db), the settings file (settings.json), and a non-running worker process. These absent components likely interrupt the proper execution of hooks and tool interactions. The environment details indicate that the issue could stem from either an incomplete initialization of a new installation or corruption/removal of essential files in an existing setup. The expected behavior is for all hooks to execute error-free, but troubleshooting will need to address the missing database, configuration, and worker process.

[jayesh-idfy]

This happened with me too. I was doing a fresh install of the plugin, and I was not able to install it. There were these above failures

[Iron-Ham]

Same: A fresh install doesn't seem to work at all.

[dayakarreddyn]

Check if you have bun installation in place, that was the cause of the error.

[jayesh-idfy]

Yep, have the bun in proper place

[adamlahbib]

Same here, fresh install:
Fixed by adding bun to the PATH in /etc/profile for sh

[thedotmack]

Triage: Multiple hook types failing simultaneously. This is likely a worker connectivity issue rather than individual hook bugs. Check if the worker is running and healthy before investigating individual hooks.

[jayesh-idfy]

So for me, the worker starts, and I can even see the page on localhost:37777. However, whenever I try to make any prompt, it fails. Upon checking one of the things that I found was the mcp-server connection always fails. I did multiple installation and uninstallation, yet it happens everytime. I checked the various paths of the bun, node, all of those things are present. Any help will be really appreciated

[thedotmack]

Closing: This issue is resolved. The hook error handling has been comprehensively hardened:

1. ensureWorkerRunning() returns false (never throws) when the worker is unavailable
2. All hook handlers (session-init, observation, user-message) check worker status and return exit code 0 on failure
3. The top-level hook command wrapper catches all exceptions and exits with code 0 (non-blocking)
4. Settings auto-create with defaults when missing
5. Database lazy-creates on first write

Hook errors no longer block the user's Claude Code session. If the worker isn't running or files are missing, hooks gracefully degrade and succeed silently.