{"version":"2.1.311","anchor":"bundle-wide-hook-and-plugin-path-changes-hooks-modules-gate","canonical_anchor":"bundle-wide-hook-and-plugin-path-changes-hooks-modules-gate","heading":"Changed check for loading hooks from installed plugins","tier":"internal","area":"Hooks","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/bundle-wide-hook-and-plugin-path-changes-hooks-modules-gate","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Changed check for loading hooks from installed plugins\n\nThe check that decides whether installed plugins' hooks load now starts with a new condition and drops an old special case\n\n**Unclear.** What the new condition checks is not known, so it is unclear whether installed plugins' hooks now load in more or fewer cases.\n\n**What**\n\nHooks are your own scripts that Claude Code runs at set moments, and plugins can bring their own. The check that decides whether hooks from installed plugins load has changed:\n\n- It now begins with a new condition and refuses to load them if that fails.\n\n- An earlier special case, for when a server-side rollout flag had not yet answered, was removed.\n\nWhen that flag has not answered, Claude Code still reports that installed plugins' hooks were not loaded, and built-in plugins load regardless.\n\n**Why**\n\nThis changes when hooks from installed plugins load while the rollout flag has not yet answered.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}