Problem: OMC hooks don't trigger (UserPromptSubmit/Stop hook error) —— Trove problem library

What you will run into

In an agent session, OMC's hooks don't trigger; on Windows, after install it reports UserPromptSubmit/Stop hook error (Issue #30 scenario). Configured but not taking effect.

Why this happens

Hook triggering is a precondition chain where all three links must hold. On an event (prompt submitted / session stopped), Claude Code locates the hook script per config.

The script must then have execute permission (+x, or exec refuses outright), and the shebang interpreter must actually run. On Windows the shebang is usually #!/bin/bash; native cmd has no bash, so Git Bash or WSL is required, and CRLF line endings also break shebang parsing.

If any precondition fails, the symptom is "configured but never fires" or "hook error".

So the check order is fixed: permission first, then interpreter environment, and only then suspect leftovers — the first step resolves most cases.

Step by step

1. Add execute permission — Required

find ~/.claude/hooks -name '*.sh' -exec chmod +x {} +

2. Windows: compatible environment + LF line endings — Required

Run hooks in a Git Bash/WSL compatible environment; make sure script line endings are LF (avoid CRLF execution errors).

3. Still erroring after reinstall: remove first, then reinstall — Required

/plugin remove oh-my-claudecode

Then install again.

How to confirm it works

Hooks trigger normally (expected shape):

Agent session submit/stop → hook logs output normally, no UserPromptSubmit/Stop hook error

Other environments

Symptom

OMC hooks do not fire in agent sessions; after install on Windows, UserPromptSubmit/Stop hook error appears (Issue #30 scenario).

Cause

1. Hook scripts lack execute permission (~/.claude/hooks/**/*.sh missing +x);
2. Shell path/escaping differences on Windows make hook scripts fail;
3. Old hooks remain after plugin reinstall.

Solution

1. Add execute permission: chmod +x ~/.claude/hooks/**/*.sh (find ~/.claude/hooks -name '*.sh' -exec chmod +x {} +).
2. Windows: run hooks in a Git Bash/WSL-compatible environment; make sure script line endings are LF (avoid CRLF execution errors).
3. If errors persist after reinstall, /plugin remove oh-my-claudecode first, then reinstall.