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.
Names in the bundlemonitorsmonitors/monitors.json
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up monitors/monitors.json, on Error reference.
* One of a plugin's [default component locations](/docs/en/plugins-reference#file-locations-reference), such as the `skills/` folder, the `monitors/monitors.json` file, or a [`SKILL.md` at the plugin root](/docs/en/plugins-reference#skills…errors see the edit
Confirmed since
Anthropic's documentation has since written up monitors, on Claude Code changelog.
* Fixed plugins silently skipping a default monitors file or root SKILL.md that could not be checkedchangelog see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up monitors, on Claude Code changelog.