You'll notice
Useful4 Signal1
Plugins you turned off stop complaining about failing to load.
What's wrong with this entry?
Anonymous. No account, no email.
What
Plugin 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.
Details
- The disabled check matches on the manifest name as well as the path, and honours plugin content authored in the repository itself.
- Applies unconditionally in the session plugin loader, with no flag or setting to turn it off.
- Loaded plugins can now also carry a server-issued plugin id.
- 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. - Credentials are now passed through the path that copies a plugin into the version cache, so authenticated sources copy rather than fail.
Evidence
Skipping load-failure error for disabled plugin, claude plugin update <plugin>@<marketplace>
Strings lifted out of the shipped bundle, so the claim above can be checked against them.