{"version":"2.1.319","anchor":"plugin-hooks-refused-file-that-names-a-module-is-flagged","canonical_anchor":"plugin-hooks-refused-file-that-names-a-module-is-flagged","heading":"Plugin hook checks now note refused files that name a module","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/plugin-hooks-refused-file-that-names-a-module-is-flagged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Plugin hook checks now note refused files that name a module\n\nWhen a plugin's hooks file is refused, Claude Code now records whether that file named a module\n\n**Unclear.** What Claude Code does differently when a refused hooks file names a module is not known.\n\n**What**\n\nPlugins can include hooks, which are commands that run at set points while Claude Code works. When Claude Code checks a plugin's hooks file and refuses it, it now records whether the refused file names a module, a piece of code the plugin wants loaded. Claude Code can also now check whether a plugin has modules or any such refused file.\n\n**Why**\n\nThis affects how plugin modules are loaded and which warnings appear.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}