automationslisted

# Automations An automation is a scheduled task. When due it runs in one of two modes: agent Spawn a thread or re-prompt a target thread with a configured prompt. script Run a stored server-side script and capture stdout/stderr/exit. Use `patcher plugin run automations ...` while the kernel `patcher automation` command still exists; once the kernel command is removed, `patcher automation ...` will route to this plugin command. Pass `--project` explicitly for every automation command. Inside a thread, automations are stamped origin `agent` and record the creating thread automatically. Automation-spawned threads cannot create automations. Choosing a mode: Use `script` when the output is fully determined by code: watchdogs, threshold alerts, health checks, heartbeats, and API pollers with a fixed output shape. Scripts run on the Patcher server, with cwd inside the plugin data directory's `scripts/` area. Script automations do not have an environment field and do not accept environment flags. Design the script to print nothing when there is nothing to report: an exit-0 run with empty stdout/stderr, or a last non-empty line of `{"wakeAgent": false}`, is recorded as a skipped silent tick. Any other output is captured; non-zero exit or timeout is recorded as a failed run. Use `agent` when the run needs reasoning: summarize a feed, pick interesting items, draft a human-friendly message, or branch on content. Creating: ```bash patcher plugin run automations create --project