{"version":"2.1.284","anchor":"plugin-install-failure-rollback-reworked","canonical_anchor":"plugin-install-failure-rollback-reworked","heading":"Failed plugin installs clean up according to why they failed","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/plugin-install-failure-rollback-reworked","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Failed plugin installs clean up according to why they failed\n\nWhen a plugin install fails, Claude Code now undoes only what that failure left behind, and can suggest updating a dependency that is too old\n\n**Unclear.** How the suggestion to update a dependency is shown to the user is not settled.\n\n**What**\n\nA plugin can depend on other plugins, and it can ask for a particular range of versions of each one. When an install fails, Claude Code now chooses what to undo based on the reason for the failure:\n\n- Version range conflict or no matching version tag on a fresh install: the dependencies it had just downloaded are removed again.\n\n- Install record could not be written: the plugin's entry in your `enabledPlugins` setting, which turns plugins on or off, is no longer reset.\n\n- Installed dependency outside the requested version range: the result now includes a suggestion to update that dependency.\n\nBefore, every failure reset the `enabledPlugins` entry in the same way. If the cleanup itself only partly succeeds, a new warning says that not everything the failed install added was removed.\n\n**Why**\n\nAn install that fails because of version-pinned dependencies should leave less half-installed material behind. The warning tells you when some of it is still there.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}