{"version":"2.1.269","anchor":"plugin-hook-modules-deferred-until-workspace-trust-is-accept","canonical_anchor":"plugin-hook-modules-deferred-until-workspace-trust-is-accept","heading":"Plugin hook modules deferred until workspace trust is accepted","tier":"notice","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/plugin-hook-modules-deferred-until-workspace-trust-is-accept","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Plugin hook modules deferred until workspace trust is accepted\n\nPlugin hooks now wait for workspace trust before loading, instead of loading unconditionally\n\n**What**\n\nClaude Code requires you to trust a workspace (a folder you're working in) before certain actions run. Now, plugin hook modules are also gated on this: if the workspace isn't yet trusted, hook modules from otherwise-loadable plugins are skipped at registration time, and Claude Code logs a message naming which hooks weren't loaded. A new session field, `hookModulesAwaitTrust`, tracks this state, and once you accept trust for the workspace, hook loading is retried and the deferred hooks register.\n\n**Why**\n\nThis prevents plugin hook code, which can run automatically at defined points, from executing in a workspace you haven't yet confirmed you trust.\n\n- Area: Plugin Hooks\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}