{"version":"2.1.287","anchor":"hooks-module-seat-no-longer-depends-on-a-process-wide-off-sw","canonical_anchor":"hooks-module-seat-no-longer-depends-on-a-process-wide-off-sw","heading":"A process-wide switch no longer decides where plugin hook modules run first","tier":"internal","area":"Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/hooks-module-seat-no-longer-depends-on-a-process-wide-off-sw","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### A process-wide switch no longer decides where plugin hook modules run first\n\nWhether the hook modules from installed plugins go first is now decided only by managed settings, a Team or Enterprise organization, or prepended plugins\n\n**Unclear.** It is not clear whether the removed off switch now applies somewhere else.\n\n**What**\n\nHooks are commands that Claude Code runs on its own at set points. Installed plugins can provide hook modules, and Claude Code decides whether those modules take the outermost position, meaning they run first.\n\nClaude Code used to skip that position when hook modules were switched off for the whole running process. That step has been removed. The position is now decided only by:\n\n- Plugins listed to go first.\n\n- Managed settings on the machine.\n\n- Belonging to a Team or Enterprise organization.\n\n**Why**\n\nTurning hook modules off for the whole process no longer stops them taking the outermost position, so the order hooks run in can differ from before.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}