{"version":"2.1.234","anchor":"plugin-load-fails-outright-when-the-cache-copy-fails","canonical_anchor":"plugin-load-fails-outright-when-the-cache-copy-fails","heading":"Plugin load fails outright when the cache copy fails","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/plugin-load-fails-outright-when-the-cache-copy-fails","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Plugin load fails outright when the cache copy fails\n\nWith the newer plugin storage layout, a failed cache copy now fails the plugin load and suggests reinstalling.\n\n**What**\n\nWith the v5 plugin storage layout pinned on for a session, a plugin whose copy into the versioned cache fails is no longer run from the marketplace clone; it fails to load with an error suggesting a reinstall. Without that layout, the old warn-and-continue behaviour is unchanged.\n\n**Details**\n\n- The fallback that ran the plugin directly from the marketplace clone is what the strict path removes.\n- Separately and unconditionally, `claude plugin` CLI failures are now split into expected failure results, which are logged, and unclassified errors, which are reported with a label naming the subcommand that produced them.\n\n**Evidence**\n\n`Not loading it from the marketplace clone (strict plugin cache).`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}