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

Claude Code v2.1.304 ·

Scheduled tasks, monitors and hook handbacks now record which plugin started them

Scheduled tasks, monitor notices and hook handbacks now carry the name of the plugin behind them

Group of 4 Under the hood Internal Changes
JSON All of v2.1.304
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
HooksArea: what it touches
Internal ChangesKind: in v2.1.304,
Internal ChangesSection of the release

Unclear It is not known whether the plugin name is shown to you or to Claude.

What

A plugin is an add-on package that extends Claude Code. Several things a plugin can start now remember which plugin started them:

  • Scheduled (cron) tasks keep an optional plugin field. It is saved with the task, kept when tasks are restored or taken over, shown in the task list and sent on the SDK event. A task whose stored plugin name breaks the naming rule is skipped. When the task fires it passes scheduledByPlugin.
  • Monitor task notifications record scheduledByPlugin. Housekeeping notices such as WebSocket closed or Monitor stopped are held back while that plugin is active, instead of always being queued straight away.
  • Handback results from a hook, which is code a plugin runs at set moments, now include plugin: hookCaller when a plugin called the hook and hookServesModel is not set.

The tool context also exposes hookServesModel and pluginUnnamed.

Why

Work a plugin starts can be traced back to that plugin, and monitors scheduled by a plugin no longer interrupt with routine notices while the plugin is running.

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 doubtIt is not known whether the plugin name is shown to you or to Claude.

See this entry in the whole of v2.1.304 →

Feedback