{"version":"2.1.242","anchor":"disabled-plugins-no-longer-report-load-failures","canonical_anchor":"disabled-plugins-no-longer-report-load-failures","heading":"Disabled plugins no longer report load failures","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/disabled-plugins-no-longer-report-load-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Disabled plugins no longer report load failures\n\nPlugins you turned off stop complaining about failing to load.\n\n**What**\n\nPlugin loading now tracks whether each entry is enabled, so a missing plugin path, a manifest that fails to load, a failed copy into the version cache or a failed download only surfaces an error when the plugin is actually turned on. Plugins you disabled stop producing noise about failing to load, while enabled ones report as before.\n\n**Details**\n\n- The disabled check matches on the manifest name as well as the path, and honours plugin content authored in the repository itself.\n- Applies unconditionally in the session plugin loader, with no flag or setting to turn it off.\n- Loaded plugins can now also carry a server-issued plugin id.\n- When a plugin installed through a command has a missing cache entry and background command execution is switched off, the error names the real update command for that plugin, `claude plugin update <plugin>@<marketplace>`, falling back to the generic form when the plugin's marketplace is not known.\n- Credentials are now passed through the path that copies a plugin into the version cache, so authenticated sources copy rather than fail.\n\n**Evidence**\n\n`Skipping load-failure error for disabled plugin`, `claude plugin update <plugin>@<marketplace>`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 1\/5"}