Follow Discord
Sweep 12 Nov 2026 · 23:00Z Build v2.1.323 540 read Stable v2.1.311 Latest v2.1.323 Next v2.1.323 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.284entry #164

Claude Code v2.1.284 ·

Failed plugin installs clean up according to why they failed

When a plugin install fails, Claude Code now undoes only what that failure left behind, and can suggest updating a dependency that is too old

You'll notice Improvements
JSON All of v2.1.284
You'll noticeTier: how much it should matter to you
1Useful: my rating, 1 to 5
1Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.284,
ImprovementsSection of the release

Unclear How the suggestion to update a dependency is shown to the user is not settled.

What

A 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:

  • Version range conflict or no matching version tag on a fresh install: the dependencies it had just downloaded are removed again.
  • Install record could not be written: the plugin's entry in your enabledPlugins setting, which turns plugins on or off, is no longer reset.
  • Installed dependency outside the requested version range: the result now includes a suggestion to update that dependency.

Before, 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.

Why

An 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtHow the suggestion to update a dependency is shown to the user is not settled.

See this entry in the whole of v2.1.284 →

Feedback