{"version":"2.1.305","anchor":"plugin-path-traversal-hint-rewritten","canonical_anchor":"plugin-path-traversal-hint-rewritten","heading":"Clearer explanation when a plugin file path is skipped","tier":"notice","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/plugin-path-traversal-hint-rewritten","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Clearer explanation when a plugin file path is skipped\n\nThe message for a skipped plugin path now says it could not be confirmed inside the plugin and mentions permission errors and backslashes in names\n\n**What**\n\nA plugin lists files it uses, and Claude Code checks that each one really sits inside the plugin's own folder. When a path fails that check, the advice shown has been rewritten. It now says the path was skipped because it could not be confirmed inside the plugin, points to permission errors such as `EACCES` (the system refusing access to a file) as a possible cause, and mentions backslashes in names.\n\nThe old text only said that files a plugin declares must resolve to a location inside the plugin.\n\n**Why**\n\nPlugin authors and users get a better idea of why a file was skipped and what to check.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}