Automations and Plugins¶
The Automations tab holds work that runs without you pressing anything: scheduled jobs, standing orders, triggers and summary exports. Plugins is a separate tab for shell steps you switch on and off.
Automations¶
Subtabs are All (the default), Exports, Cron jobs, Standing orders, Triggers and Processes.
Lists have a filter bar, sortable columns and page sizes from 25 to 200. Use + new cron job and + new standing order to add one. A badge on the tab counts active exports.
Exports¶
Conversation summary jobs, with a progress stepper and a download. Start one from
an agent's ⚙ menu with summary…. dismiss deletes the delivered file.
Cron jobs¶
Send a message or start an agent on a schedule, as an interval of 30 seconds or more, or a cron expression. Each job has run-now, a recent-runs log, edit, duplicate, enable and delete.
Spawn jobs take a spawn profile, roles and a concurrency rule: Forbid, Replace (stop the live worker first), or Allow with a max number of live workers.
The CLI equivalent is tclaude agent cron.
Standing orders¶
Standing instructions tied to events: session start, a user prompt, or before or after a tool, plus each harness's own hooks. You can add a condition on the directory, prompt, tool name or tool input, and set delivery, cadence, minimum interval and debounce. Each target shows whether it is supported, degraded or unsupported.
Triggers¶
Rules on PR opened, updated or merged, CI failed or succeeded, or an agent going idle or awaiting input. A rule starts an agent or sends a templated message, and is scoped globally or to a group. Each is armed, cooling or disabled.
A worker launches from its spawn profile, then the group's default profile,
then the global default profile, as a direct spawn naming that profile would.
That covers its roles, role label, description, saved prompts and startup
context, and the ownership and permission overrides it is born with. A rule
owned by an agent confers only what that agent may grant: a default profile's
grant or ownership the owner lacks the authority for is skipped, and the
firing's detail says so, while the same on the worker's own profile refuses
the firing (permission_denied).
If any of those profiles is disabled, or is operator-only and an agent owns
the job or rule, the run is refused: it shows as failed in the job's recent
runs or the trigger's firing history (profile_disabled or
profile_operator_only, with the profile's name). The first refusal also
sends a notice to the owning agent and to your Messages tab. Later identical
refusals are only recorded, until a run spawns again or the daemon restarts.
Processes¶
/automations/processes lists process templates and opens the graph editor. Runs
are not listed here; they live in Groups.
The list has rename, describe, versions, delete, import and export, and Edit with agent hands a template to a scribe agent. The editor has these node types: Task, Decision, Parallel, Wait, Subprocess, Start and End. Other highlights:
- Get help ▾ brings in the template's scribe, or an agent already running, in its regular overlay chat window, and sends it the selection, a node or an issue to look at. A version the scribe saves is reviewed on the canvas, change by change: A accept, R reject, J and K to walk.
- Subprocess nodes (▣): double-click to drill in, and Esc or Alt ↑ to leave. ⇪ extracts a body as its own template, ⊞ expands it in place, ▣ wraps a selection, ⇲ unwraps one.
- Drop a palette item onto a connector to splice it in.
See Processes for the whole flow.
For automation workflows, see Teams at scale.
Plugins¶
The Plugins tab appears when you have a plugin. To keep it visible anyway, turn on Plugins tab in Config › Appearance.
A plugin is a named list of shell steps (check, run, stop) with a status lamp: active, not active, off, still active or unknown. Click a step's lamp to run or stop it. check runs one plugin's checks, and check all runs everything. Checks also repeat every minute. A warning badge on the tab counts problems. You can also edit plugins and install them from the catalog.