{"version":"2.1.238","anchor":"unreadable-plugin-hook-files-are-reported-instead-of-skipped","canonical_anchor":"unreadable-plugin-hook-files-are-reported-instead-of-skipped","heading":"Unreadable plugin hook files are reported instead of skipped","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/unreadable-plugin-hook-files-are-reported-instead-of-skipped","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Unreadable plugin hook files are reported instead of skipped\n\nA plugin whose hooks file cannot be read now shows a load failure instead of silently doing nothing.\n\n**What**\n\nIf 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.\n\n**Details**\n\n- The failure is recorded as a `hook-load-failed` entry.\n- The file-existence probe now attaches the error detail to its unusable result so the error code can be included.\n- The advice text was broadened to \"Check the plugin's hooks configuration and that its hooks file is readable\".\n\n**Evidence**\n\n`Check the plugin's hooks configuration and that its hooks file is readable`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}