{"version":"2.1.287","anchor":"hook-origin-guard-and-watch-path-api","canonical_anchor":"hook-origin-guard-and-watch-path-api","heading":"Hook modules can retry loading, and hooks without an origin pass through","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/hook-origin-guard-and-watch-path-api","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Hook modules can retry loading, and hooks without an origin pass through\n\nModules that provide hooks can now retry ones that failed to load, and the hook file watcher can be given more paths\n\n**Unclear.** It is not clear what, if anything, a user sees change from this.\n\n**What**\n\nA hook is a script Claude Code runs automatically at certain points. Several parts of how hooks are handled changed:\n\n- A hook event with no recorded origin is now passed on unchanged.\n\n- The watcher that looks for changes to environment hooks can be given more paths to watch.\n\n- Modules that provide hooks can now retry loading modules that failed to load earlier.\n\n**Why**\n\nA hook module that failed to load can be tried again instead of staying unloaded.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}