{"version":"2.1.299","anchor":"hooks-module-reload-helpers-replace-mcpxaaidploginmodule-acc","canonical_anchor":"hooks-module-reload-helpers-replace-mcpxaaidploginmodule-acc","heading":"Claude Code gains helpers to reload or stand down plugin hooks","tier":"internal","area":"Hooks","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/hooks-module-reload-helpers-replace-mcpxaaidploginmodule-acc","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code gains helpers to reload or stand down plugin hooks\n\nNew internal helpers can reload plugin hooks, warn the session, and stand down installed hooks modules while Claude Code is running\n\n**Unclear.** It is not clear when these helpers run or whether they are switched on for anyone.\n\n**What**\n\nHooks are small scripts or programs, often supplied by plugins (add-on packages for Claude Code), that run automatically at set points in a session. A session is one run of Claude Code from start to finish. Claude Code now has a set of helpers for managing them while it is running:\n\n- Reloading plugin hooks\n\n- Showing a warning in the session\n\n- Standing down installed hooks modules, which stops them from taking part\n\n- Handling a session that opens, ends or fails\n\nThey replace a smaller piece of code that did none of this.\n\n**Why**\n\nThis affects how hooks are reloaded or switched off while Claude Code is running, so a change to your hooks could take effect, or stop taking effect, without a restart.\n\n- Area: Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}