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

Claude Code v2.1.242 ·

Plugin hook modules run in an isolated sandbox with time and size budgets

Plugin hook modules run in a locked-down sandbox with time and size limits.

Nothing to try yet In Development
JSON All of v2.1.242
Nothing to try yetTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
PluginsArea: what it touches
In DevelopmentKind: in v2.1.242,
In DevelopmentSection of the release

Sandbox isolation ships with the plugin hook-module feature, which is off.

What

When the plugin hook-module feature is enabled, each module runs in its own JavaScript context that cannot generate code, cannot import outside its own plugin folder, and is stopped if it overruns.

Details
  • Console output is routed into the hook chain report; setTimeout and setInterval are shimmed and cancelled when the plugin unloads.
  • Imports are limited to relative paths inside the plugin directory plus one synthetic types module; TypeScript and TSX sources are transpiled with Bun.
  • Handlers get a budget that can be paused and resumed, and an abort grace period after which the hook is reported as a runaway.
  • Matcher copying is capped by node count and nesting depth; values passed across the boundary are deep-frozen or cloned.
  • Same off-by-default gate as the capability object; nothing here can be switched separately.
Evidence

core table: not an operation

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

Feedback