What
Plugins can now define persistent background monitors that stream events into the conversation as <task_notification> events.
Details
- Define monitors in a
monitors/monitors.jsonfile at the plugin root, or inline via themonitorsfield inplugin.json - Each monitor has:
id(unique within plugin),description,command(shell command), and anarmTrigger - Arm triggers control when monitors start:
"always"— arms at session start and on plugin reload"on-skill-invoke:<skill>"— arms the first time a specific skill is dispatched- Each stdout line from the monitor command becomes a notification; stderr goes to an output file
- Monitor IDs are deduped to prevent duplicate spawns on reload
- Session-scoped: monitors stop when the session ends
Evidence
Monitor schema (search for "monitors.json") and arm triggers (search for "on-skill-invoke")
Strings lifted out of the shipped bundle, so the claim above can be checked against them.