Source Intelligence

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.228 Home All releases olderv2.1.227 v2.1.229newer
Claude Code v2.1.228

Plugin in-use markers get their own directory and escape checks

Under the hood
Useful1 Signal1
Plugins

Plugin in-use markers now live in their own folder and cannot escape the plugins directory.

What

The per-process marker that records a linked plugin as in use is now written under a dedicated .in_use-links directory whose resolved path must stay inside the plugins directory.

Details
  • Each path component is created and re-resolved against the real filesystem path; if any step resolves outside, the marker is not written and the scan is skipped, with a log naming the offending path.
Evidence

.in_use-links

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.228 →