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.232 Home All releases ←olderv2.1.231 v2.1.233newer→
Claude Code v2.1.232

Plugin registry can be read through the storage backend

Under the hood
Useful1 Signal3
Plugins

The installed-plugins file can be loaded through the storage layer, upgrading old registry formats.

What

Loading the installed-plugins file gained an asynchronous path that goes through the v5 storage layer rather than reading from disk directly, upgrading old V1 registry files to V2 as it loads.

Details
  • Results are cached under an epoch counter so a concurrent synchronous load takes precedence.
  • Storage backend failures are mapped to a dedicated registry error, and a defensive error covers a read that completes without an outcome for its key.
  • Nothing in this build shows the new path replacing the existing synchronous load.
Evidence

installed plugins registry read settled without an outcome for its key

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

See this entry in the whole of v2.1.232 →