{"version":"2.1.292","anchor":"managed-plugin-entries-kept-if-directory-bindings-file-unusa","canonical_anchor":"managed-plugin-entries-kept-if-directory-bindings-file-unusa","heading":"Stale managed plugin entries are kept, with a warning, when the directory-bindings file is unusable","tier":"notice","area":"Plugins","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/managed-plugin-entries-kept-if-directory-bindings-file-unusa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Stale managed plugin entries are kept, with a warning, when the directory-bindings file is unusable\n\nClaude Code no longer removes outdated managed or duplicate plugin entries unless it can use plugin-directory-bindings.json, and it now warns when it keeps them\n\n**What**\n\nManaged plugins are plugins that an organisation's policy requires to be installed. When policy no longer requires one, or an entry is a duplicate, Claude Code tidies up the leftover entry.\n\n- Removing such entries now needs `plugin-directory-bindings.json` in the plugins folder, a file that records which repository each plugin was installed from.\n\n- If that file cannot be used or written, the stale managed or duplicate entries are kept instead of being removed.\n\n- When this happens, a warning is now logged. Before, entries were removed without this check, and nothing was said.\n\n**Why**\n\nIf you see leftover plugin entries after an install, the warning explains why they are still there. The cleanup also no longer goes ahead without being able to record where the plugin came from.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: yes"}