Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.234 Home All releases ←olderv2.1.233 v2.1.235newer→
Claude Code v2.1.234

Plugin config reads go through the newer storage layer, and failures are attributed

Under the hood
Useful1 Signal2
Plugins

Plugin install, update and enable now read their config through the newer storage layer, with the old path as backup.

What

Plugin autoupdate, install, uninstall, prune and enable/disable now read plugin configuration asynchronously through the newer storage layer, falling back to the old synchronous read when that layer is off or unavailable.

Details
  • Several error handlers in this area that previously swallowed failures silently now report them with context, so a failed toggle surfaces as /plugin: toggling a plugin on the list threw rather than disappearing, and a failed scan for orphans after an uninstall is attributed too.
  • One internal error type is excluded from generic error reporting.
Evidence

/plugin: toggling a plugin on the list threw

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.234 →