claude-code - 💡(How to fix) Fix Hook errors for PreToolUse:Agent / PostToolUse:Agent surface cryptic "command not found" output [2 comments, 2 participants]

⎿ PreToolUse:Agent hook error ⎿ PostToolUse:Agent hook error

1. The hook matcher in settings is "Task" (matching Claude Code's documented tool name), but the error header reports the tool as Agent. This mismatch between the configured matcher and the reported tool name makes it non-obvious which hook entry is failing and which tool triggered it.
2. The error is labelled "non-blocking status code", but each failing invocation still prints a multi-line error block in the transcript for every single Agent call, which is visually noisy and gives little actionable information (no hook index, no matcher, no command string). With entire not installed / not on the hook process's PATH, any use of the agent tool produces the error shown above.

• The hook error output includes the failing hook's matcher and the resolved command string, so the user can identify which hook to fix, or
• The tool-name label in the error header uses the same identifier (Task vs Agent) that users are expected to put in matcher, so the config and the diagnostic stay in sync, or

TL;DR

Update the matcher in the hook settings to match the actual tool name reported in the error header, which is Agent, or ensure the command is resolvable on the PATH used by the hook execution environment.

Guidance

• Verify that the command entire is installed and available on the PATH of the non-login /bin/sh shell used for hook execution.
• Consider modifying the matcher in the hook settings to use the tool name Agent instead of Task to match the error header.
• To reduce visual noise, explore options for coalescing non-blocking hook failures into a single warning per session, such as modifying the hook execution script or the Claude Code CLI configuration.
• Ensure that the environment variables and PATH settings are correctly configured for the hook execution environment, which may differ from the interactive shell environment.

Example

No code snippet is provided as the issue is more related to configuration and environment setup.

Notes

The issue seems to be related to the mismatch between the configured matcher and the actual tool name reported in the error header, as well as the command not being resolvable on the PATH. The solution may involve updating the matcher or ensuring the command is available on the PATH.

Recommendation

Apply workaround: Update the matcher to match the actual tool name Agent or ensure the command is resolvable on the PATH, as this seems to be the most straightforward way to address the issue.