{"version":"2.1.140","anchor":"plugin-folder-shadowing-warnings","canonical_anchor":"plugin-folder-shadowing-warnings","heading":"Plugin Folder-Shadowing Warnings","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140\/e\/plugin-folder-shadowing-warnings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.140","markdown":"### Plugin Folder-Shadowing Warnings\n\n**What**\n\nClaude Code now surfaces a warning when a `plugin.json` manifest field shadows the corresponding default auto-loaded folder, and tells the plugin author how to fix it.\n\n**Details**\n\n- Warning message: `\"Default <component>\/ folder is ignored because plugin.json sets '<manifestField>'\"`.\n- Suggested fix: `\"Remove '<manifestField>' from plugin.json to auto-load the folder, or add the folder's files to the '<manifestField>' list if you want both\"`.\n- Warnings are categorized separately from hard errors (`plugin_errors`) \u2014 a warned plugin still loads and is present in `plugins[]`.\n- Warnings now appear in the UI via the `plugins.warnings` state that the plugin panel reads.\n\n**Evidence**\n\n`PE()` and `te$()` functions (search for `\"folder-shadowed-by-manifest\"`)"}