{"version":"2.1.248","anchor":"plugins-can-declare-background-monitors","canonical_anchor":"plugins-can-declare-background-monitors","heading":"Plugins can declare background monitors","tier":"use","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/plugins-can-declare-background-monitors","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Plugins can declare background monitors\n\nPlugins can ship background monitors that run as persistent unsandboxed tasks; install only trusted ones.\n\n**What**\n\nPlugins 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.\n\n**Details**\n\n- The host arms declared monitors as long-lived tasks at plugin load.\n- Same trust tier as hooks means no sandboxing and no separate consent step.\n\n**Evidence**\n\n`unsandboxed, same trust tier as hooks`\n\n- Area: Plugins\n- Names: `monitors`, `monitors\/monitors.json`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 5\/5"}