You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.305,
ImprovementsSection of the release
What
A 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.
The old text only said that files a plugin declares must resolve to a location inside the plugin.
Why
Plugin authors and users get a better idea of why a file was skipped and what to check.
