Templates
Templates are pre-configured automation rules you can activate with a click. Each ships with a tested trigger, execution surface, model config, guardrails, and prompt — every field is editable after creation. Navigate to Automations → Templates to browse them.Templates whose execution surface is a Worker run show a “Coming soon” chip in packaged builds and the Use Template button reads “Coming Soon” with a tooltip explaining why. The card is still visible so you can see the shape of the rule and plan around it.
Built-in templates
Daily Agent Brief
Trigger:
schedule — weekdays at 9am.
Execution: Agent session.Summarizes repo activity since the last weekday brief — commits, PRs, worker runs, and risk signals — in an automation-only chat thread. Pulls repo state and procedures as context.PR Review Session
Trigger:
git.pr_opened on main.
Execution: Agent session.Reviews every new PR for risky changes, missing tests, and release impact. Posts findings citing specific files and checks, with high thinking level for thorough analysis.Linear Triage Worker run
Trigger:
linear.issue_created (team: ENG).
Execution: Worker run (disabled in packaged builds).Launches a triage worker run on new Linear issues — owner, severity, next action — using worker run-level tooling. In production builds the card shows “Coming soon” until Workers ships.Nightly Test Sweep
Trigger:
schedule — weekdays at 2am.
Execution: Built-in (run-tests).Runs your configured test suite without starting a chat or worker run. Results are saved as automation artifacts. Requires a test suite ID in project config.Push Conflict Scan
Trigger:
git.push on main.
Execution: Built-in (predict-conflicts).Runs conflict prediction after every push to the default branch, so at-risk lanes surface before they block work.Using a template
1
Browse
Open Automations → Templates. Each card shows trigger, execution kind, and a short summary.
2
Use Template
Click Use Template. ADE creates a new rule pre-filled with the template’s configuration and opens it in the editor. (For a worker run-based template in a packaged build the button reads Coming Soon and is disabled.)
3
Customize
Adjust trigger conditions, prompt, model, guardrails, and outputs. Built-in rules expose a Target lane dropdown at the top of the action editor — leave it on the default to auto-select from the trigger or primary lane, or pick a specific lane.
4
Enable
Toggle the rule to enabled. It fires on the next matching trigger.
Template anatomy
Every template produces a rule with these fields:Outputs and routing
Automations can produce several output types. Configure routing in the rule’s settings to control where results land.Output disposition
- Comment-only — results are stored as artifacts and optionally posted as comments (PRs, Linear, lane chats). No code changes.
- Commit — the automation can make code changes and commit them. For rules like dependency updates.
- Draft PR — the automation creates a draft PR for human review.
Viewing automation runs
The History tab lists every run with its status, trigger, duration, and cost. Run rows now support direct navigation — if a run executed as a worker run, the detail panel includes a link that opens the worker run in the Workers view. Rows are filterable by rule, status, and time window. Errors are surfaced inline; you don’t have to open the detail panel to see that something failed.Creating custom templates
ADE does not yet ship custom template authoring. To replicate a rule with different parameters, right-click an existing rule → Duplicate, then modify the copy.Next steps
Automation rules guide
Step-by-step walkthrough for authoring custom automation rules.
Guardrails
Safety limits, review modes, and intervention policies.