{"version":"2.1.321","anchor":"managed-settings-marketplace-take-back-withholds-cached-plug","canonical_anchor":"managed-settings-marketplace-take-back-withholds-cached-plug","heading":"Withdrawing a managed marketplace's plugins now stops if the plugin list cannot be read","tier":"notice","area":"Plugins","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/managed-settings-marketplace-take-back-withholds-cached-plug","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Withdrawing a managed marketplace's plugins now stops if the plugin list cannot be read\n\nPlugins from a marketplace named in managed settings are taken back, unless installed_plugins.json cannot be read, which stops it with an error\n\n**What**\n\nA plugin marketplace is a source plugins are installed from. Managed settings, which an organisation's administrator controls, can name a marketplace. Claude Code then takes back that marketplace's plugins, removing them from its plugin cache (the local copies it keeps) and from installed_plugins.json, the file listing installed plugins.\n\nIf installed_plugins.json cannot be read, Claude Code now holds the take-back back and shows an error saying it could not withdraw the cached plugins. Before, it removed every plugin from that marketplace with no such check.\n\n**Why**\n\nThis gives administrators a safer way to enforce marketplace rules. If you see this error, check that installed_plugins.json is readable.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}