Problem
On Claude Code native Windows, the Warp plugin hook commands execute shell scripts directly, for example:
"command": "${CLAUDE_PLUGIN_ROOT}/scripts/on-post-tool-use.sh"
When a PostToolUse hook fires, Windows treats the .sh path as a file to open instead of executing it with Bash. This repeatedly opens the Windows app picker dialog asking which application should open .sh files.
Reproduction
- Install/use the Warp Claude Code plugin on Windows native Claude Code.
- Trigger a tool call so
PostToolUse runs.
- Windows opens the app picker dialog for the
.sh file.
Expected behavior
Hook scripts should be invoked through Bash on Windows, so they run silently and do not trigger the app picker.
Proposed fix
Wrap the hook script commands with bash, for example:
"command": "bash \"${CLAUDE_PLUGIN_ROOT}/scripts/on-post-tool-use.sh\""
I opened a PR with this change.
Problem
On Claude Code native Windows, the Warp plugin hook commands execute shell scripts directly, for example:
When a
PostToolUsehook fires, Windows treats the.shpath as a file to open instead of executing it with Bash. This repeatedly opens the Windows app picker dialog asking which application should open.shfiles.Reproduction
PostToolUseruns..shfile.Expected behavior
Hook scripts should be invoked through Bash on Windows, so they run silently and do not trigger the app picker.
Proposed fix
Wrap the hook script commands with
bash, for example:I opened a PR with this change.