{"version":"2.1.317","anchor":"hook-fix-messages-for-csh-makefile-and-awk-scripts","canonical_anchor":"hook-fix-messages-for-csh-makefile-and-awk-scripts","heading":"Blocked hooks now explain csh, makefile and awk scripts","tier":"notice","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/hook-fix-messages-for-csh-makefile-and-awk-scripts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Blocked hooks now explain csh, makefile and awk scripts\n\nWhen Claude Code blocks a hook, it now has reasons for scripts that may run through csh or tcsh, makefiles and awk scripts\n\n**What**\n\nA hook is an action you set up to run automatically at a certain point in a session. When Claude Code blocks a hook, it explains why. It now has three more reasons, each for a script it cannot check on your machine:\n\n- The script may run through csh or tcsh, two older shells.\n\n- The script is a makefile.\n\n- The script is an awk script, and what awk would run from it cannot be checked.\n\n**Why**\n\nHooks of these kinds are refused with a clear reason, so you know what to change instead of guessing why the hook did not run.\n\n- Area: Hooks\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}