Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.228 ·

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

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

Under the hood Improvements
JSON All of v2.1.228
Under the hoodTier: 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.228,
ImprovementsSection of the release
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 →

Feedback