Follow Discord
Sweep 08 Oct 2026 · 18:53Z Build v2.1.295 516 read Stable v2.1.286 Latest v2.1.295 Next v2.1.295 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.290 ·

Waiting plugin toasts now give way to the same plugin's newer ones

A plugin toast that is still waiting to be shown is now replaced by that plugin's newer toasts, and toast text passes through a sanitizer

Group of 2 You'll notice Improvements
JSON All of v2.1.290
You'll noticeTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
PluginsArea: what it touches
ImprovementsKind: in v2.1.290,
ImprovementsSection of the release

Unclear The exact rules for when a plugin toast waits and when it replaces another are not settled.

What

A toast is a small pop-up notification. Plugins, which are add-ons that extend Claude Code, can show them. This release changes how a plugin's toasts line up and replace one another.

  • Plugin toasts now carry a per-plugin key and two ordering settings, waitsItsTurn and invalidates, when toasts are not stacked. Before, the key was plugin-toast-${...} and there were no ordering settings.
  • A plugin toast that is still waiting to be shown gives way to that plugin's newer toasts, so the older one is dropped without ever appearing. A debug note records this.
  • New helpers manage a stack of toasts. They cap how many toasts the stack can hold and log any toast that leaves the stack before it was drawn.
  • Toast and status text now passes through a sanitizer, a step that cleans up text before it is shown.

Why

When a plugin sends several notifications in a row, you now see its latest one instead of a backlog of out-of-date ones. Plugin authors should expect toasts that were queued and then replaced to never appear.

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 exact rules for when a plugin toast waits and when it replaces another are not settled.

See this entry in the whole of v2.1.290 →

Feedback