Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.271 ·

ui.render invalidation now distinguishes 'live' vs 'steady' pace

Plugin UI re-rendering now runs at two different paces, 'live' and 'steady', instead of one fixed rate

TierUnder the hoodhow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaPlugin UIwhat it touches
KindInternal Changesin v2.1.271,
Under the hood

Plugin UI re-rendering now runs at two different paces, 'live' and 'steady', instead of one fixed rate

What

The scheduler that decides when to re-render or invalidate a plugin's user interface previously debounced all updates at a single fixed interval. It now tracks two separate paces: a short 'live' interval and a longer 'steady' interval. The faster 'live' pace only kicks in when a specific predicate is met, and updates that use it are tagged with '... live' in the shared render-count tracking used elsewhere for cross-instance request validation.

Why

Splitting rendering into two paces lets parts of the UI that need to feel responsive update quickly while the rest updates at a calmer rate, likely reducing unnecessary redraw work compared to a single fixed interval for everything.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtThe specific condition that triggers the faster 'live' pace isn't identified.

See this entry in the whole of v2.1.271 →

Feedback