You'll notice
Useful3 Signal2
A plugin whose hooks file cannot be read now shows a load failure instead of silently doing nothing.
What's wrong with this entry?
Anonymous. No account, no email.
What
If Claude Code cannot tell whether a plugin's hooks/hooks.json exists, that is now logged as an error and surfaced as a load failure with the hook path and the underlying system error code, rather than being treated the same as the file simply not being there.
Details
- The failure is recorded as a
hook-load-failedentry. - The file-existence probe now attaches the error detail to its unusable result so the error code can be included.
- The advice text was broadened to "Check the plugin's hooks configuration and that its hooks file is readable".
Evidence
Check the plugin's hooks configuration and that its hooks file is readable
Strings lifted out of the shipped bundle, so the claim above can be checked against them.