{"version":"2.1.288","anchor":"plugin-hooks-module-loading-restructured-around-a-gate-check","canonical_anchor":"plugin-hooks-module-loading-restructured-around-a-gate-check","heading":"Claude Code chooses which hook modules to load in a different way","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/plugin-hooks-module-loading-restructured-around-a-gate-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Claude Code chooses which hook modules to load in a different way\n\nThe way Claude Code decides which hook modules to load now takes a simpler path in some cases and reads its hook settings in one place\n\n**Unclear.** What decides which of the two paths is taken, and what the simpler path does, is not known.\n\n**What**\n\nHooks are commands you or a plugin set up to run automatically at certain points. The way Claude Code picks which hook modules to load has been reworked. In some cases it now takes a simpler path. Otherwise it applies the same filtering as before, but the settings that turn hooks off, limit them to managed ones or turn them all off are now gathered in one place instead of being passed one by one.\n\n**Why**\n\nThis can affect which hooks load and when hooks are treated as turned off.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}