Sweep 19 Sep 2026 · 02:36Z Build v2.1.278 500 read Stable v2.1.267 Latest v2.1.278 Next v2.1.278 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.267 ·

New sandboxed renderer lets plugin UI components (Button/Input/Select) safely rewire closures, plus a reworked hook-chaining framework with call-count throttling

Plugin UI components like Button, Input and Select now run in a sandboxed renderer that safely reattaches event handlers

TierUnder the hoodhow much it should matter to you
Useful3my rating, 1 to 5
Signal3worth watching, 1 to 5
AreaPlugin UIwhat it touches
KindInternal Changesin v2.1.267,
Under the hood

Plugin UI components like Button, Input and Select now run in a sandboxed renderer that safely reattaches event handlers

What

Plugins that render their own UI (using components like Button, Input and Select) now go through a new sandboxed renderer. When a plugin's UI tree is built, its event handlers (like onPress on a Button, or onInput/onSubmit on an Input) get frozen and passed across a sandbox boundary, then safely reattached ("rewired") afterward so they still work.

Alongside this, the underlying system that lets plugins chain together hooks (functions that run in response to events, using an on(event).catch() style registration) was reworked. Each hook now has a call-count limit, and once a hook is called too many times it is throttled, with a one-time warning logged.

Why

This lets plugin-authored UI safely run in a restricted sandbox without losing the ability to respond to clicks, typing, and submissions, while the call-count throttling guards against a misbehaving hook being invoked in a runaway loop.

See this entry in the whole of v2.1.267 →