{"version":"2.1.288","anchor":"plugin-hooks-re-read-plugins-when-plugin-affecting-settings","canonical_anchor":"plugin-hooks-re-read-plugins-when-plugin-affecting-settings","heading":"Plugins are read again if their settings change while hooks are being set up","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/plugin-hooks-re-read-plugins-when-plugin-affecting-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Plugins are read again if their settings change while hooks are being set up\n\nIf settings that affect plugins change while Claude Code is loading them, it now reads the plugins again before choosing which hooks to run\n\n**Unclear.** It is not clear how often the extra read happens in practice or whether you would notice it.\n\n**What**\n\nPlugins are add-ons that extend Claude Code, and some supply hooks, which are scripts that run automatically at set points during a session. Claude Code now notes the plugin-related settings in force when it starts reading your plugins. If those settings have changed by the time it picks which plugin hooks to use, it reads the plugins again first. It also reads again if it cannot work out which settings it started under.\n\nMore settings now count as plugin-affecting. Alongside enabled plugins, plugin configuration, trusted sources, marketplaces and policy settings, these now include:\n\n- vouching settings\n\n- `disablePluginDirectory`\n\n- `disableCommandPluginSources`\n\n**Why**\n\nThis stops Claude Code from picking plugin hooks based on settings that were already out of date, for example after a managed policy setting changed partway through loading.\n\n- Area: Plugins\n- Names: `disableCommandPluginSources`\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}