Skip to main content

​
Overview

Automations is ADE’s background execution layer. Each automation is a Trigger → Execution rule. When a trigger fires, ADE executes through one of three surfaces:
  • agent-session — an automation-only AI chat thread with scoped tools.
  • worker run — a delegated worker run with phases, workers, and intervention support. (Paused in packaged builds until Workers ships; see the Execution Surfaces page.)
  • built-in — an ADE-native operation (tests, conflict prediction, status sync) with no chat session. Can target a specific lane or auto-select from the trigger.
The trigger can come from a schedule (schedule) or an action event (webhook, github.webhook, git.push, git.commit, manual run).

Event-Driven

Time-based (cron) and action-based triggers fire automatically based on events from git, files, webhooks, and user actions.

Execution Surfaces

Choose between Agent Session, Worker run, and Built-In Task based on autonomy and audit needs.

Configurable Guardrails

Budget caps, scoped tools, dry-run mode, and verification gates keep automation outcomes controlled.

Built-in Templates

ADE ships with PR Reviewer, Test Guardian, Daily Standup, and more out of the box.

​
Trigger Types

​
Local Git & File Events

​
Explore Automations

Execution surfaces

Learn about agent-session, worker run, and built-in execution and how to pick the right one.

Templates & Outputs

Browse built-in automation templates and configure output routing.

Guardrails & Security

Tool palette security, execution guardrails, budget controls, and troubleshooting.