Source Intelligence
Follow Discord

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

← All of v2.1.248 Home All releases ←olderv2.1.247 v2.1.250newer→
Claude Code v2.1.248

Plugins can declare background monitors

Use it now
Useful4 Signal5
Plugins Notable

Plugins can ship background monitors that run as persistent unsandboxed tasks; install only trusted ones.

monitorsmonitors/monitors.json
What

Plugins can now ship background monitors. The schema gains a monitors field that is either a path to a JSON file relative to the plugin root or an inline array, defaulting to monitors/monitors.json when omitted. Monitors run as persistent tasks with the same trust as hooks: unsandboxed, so only install them from plugins you trust.

Details
  • The host arms declared monitors as long-lived tasks at plugin load.
  • Same trust tier as hooks means no sandboxing and no separate consent step.
Evidence

unsandboxed, same trust tier as hooks

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

Related

Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.

See this entry in the whole of v2.1.248 →