{"version":"2.1.283","anchor":"plugin-failures-with-id-or-install-record-problems-now-repor","canonical_anchor":"plugin-failures-with-id-or-install-record-problems-now-repor","heading":"Plugin errors about bad IDs or unreadable install records are classed as validation","tier":"internal","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/plugin-failures-with-id-or-install-record-problems-now-repor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Plugin errors about bad IDs or unreadable install records are classed as validation\n\nFour plugin failure types, such as an invalid plugin ID, are now reported as validation errors in Claude Code's error reports\n\n**Unclear.** Whether the new category also changes any message shown on screen was not checked.\n\n**What**\n\nWhen a plugin operation fails for one of these reasons, Claude Code now labels the failure as a validation error:\n\n- `invalid_plugin_id`\n\n- `install_records_unreadable`\n\n- `directory_identity_changed`\n\n- `directory_binding_unreadable`\n\nThis label is applied first. Before, the category was guessed from the wording of the error message, which could class it as a network or policy problem. The label goes into the usage reports Claude Code sends about plugin events, such as automatic plugin updates and the removal of plugins that are no longer listed.\n\n**Why**\n\nThis mostly changes how failures are counted in reports. You will probably see little difference when using plugins.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}