{"version":"2.1.239","anchor":"skipped-plugin-warning-no-longer-overstates-what-it-found","canonical_anchor":"skipped-plugin-warning-no-longer-overstates-what-it-found","heading":"Skipped-plugin warning no longer overstates what it found","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/skipped-plugin-warning-no-longer-overstates-what-it-found","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### Skipped-plugin warning no longer overstates what it found\n\nThe untrusted-project dialog no longer overstates skipped plugins and points at \/reload-plugins.\n\n**What**\n\nWhen you open an untrusted project, the trust dialog now says directories that may load as plugins were skipped, rather than asserting they are plugins, and points at `\/reload-plugins` to load whichever ones qualify.\n\n**Details**\n\n- Plugin discovery validates each candidate through a check instead of reading a `.claude-plugin` directory unconditionally.\n- Discovery yields to the event loop between directories, so scanning a project with many candidates does not block the interface.\n\n**Evidence**\n\n`that may load as ${d === 1 ? \"a plugin\" : \"plugins\"}`\n\n- Area: Plugins\n- Names: `\/reload-plugins`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 1\/5"}