{"version":"2.1.305","anchor":"plugin-manifest-monitors-and-settings-reads-refuse-paths-th","canonical_anchor":"plugin-manifest-monitors-and-settings-reads-refuse-paths-th","heading":"Plugins can no longer read their manifest or settings from outside their folder","tier":"notice","area":"Plugins","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/plugin-manifest-monitors-and-settings-reads-refuse-paths-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Plugins can no longer read their manifest or settings from outside their folder\n\nClaude Code now refuses to load a plugin whose manifest, monitors or settings file links to a location outside the plugin's folder\n\n**Unclear.** It is not clear whether this check applies to plugins from every source or only some.\n\n**What**\n\nWhen Claude Code loads a plugin, it now checks that these files really sit inside the plugin's own folder:\n\n- the plugin manifest, the file that describes the plugin\n\n- `monitors\/monitors.json`\n\n- `settings.json`\n\nThe check matters when the plugin uses a symlink or junction, which is a shortcut that makes a file appear in one place while it lives in another. If the manifest points outside the folder, the plugin is not loaded and you see a message beginning \"Plugin not loaded: its manifest\". Before, these files were read directly with no such check.\n\n**Why**\n\nThis is a security safeguard. It stops a plugin from pulling files from elsewhere on your computer. If a plugin you use relies on shortcuts that point outside its folder, it may stop loading.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: yes"}