Automation for Projects

Projects has three kinds of automation: agents you run on tasks and epics, flows that react to task and repository events, and built-in rules that keep epics and sprints up to date. This page shows what's available and where to set it up.

Run agents on tasks and epics

• On a task, choose an agent and select Run. The task shows the run's progress and what it needs from you.

• On an epic, choose an agent and select Run. Use Add special instructions to guide the run.

• You can also start any agent from Automation → Agents with Run now and pick a task or epic as the target.

Built-in agents for project work include:

Agent	Use it to
Atlas	Plan an epic.
Scribe	Plan and organize tasks.
Forge	Build code changes for a task.
Lens	Review code changes.

Forge and Lens are coding agents, which are not available in the Community edition. See Coding runs and delivery.

Automate with flows

Flows start work when something happens. Triggers useful for projects include:

• Task enters a workflow state

• Interactive run is approved

• GitHub and GitLab events, such as a pull request merging or a check suite completing

• Schedule ticks, for recurring work

A flow can start an agent run, move a task to another state, or merge a task branch. See Flows overview and Start a flow when a task changes state.

Start from a template

In Automation → Flows, select Browse templates. Templates for project work include:

Template	What it does
Advance on approval	Moves a task forward when an interactive agent run is approved.
Merge when done	Merges a task branch when the task enters the selected done state.
Stale task escalation	Finds stale tasks on a schedule and posts or creates follow-up work.

Built-in project rules

These rules run without a flow. Configure them in Settings → Projects → Automations.

Rule	What it does
Auto Start Epic	Moves an epic to the state you choose when one of its tasks enters a started state.
Auto Complete Epic	Moves an epic to the state you choose when all of its tasks are done.
Sprint automation	Keeps future sprints available and moves unfinished work into the next sprint, for teams that use sprints. Set this up in each team's settings.

Keep tasks in step with pull requests

Teams can map pull request events to workflow states, so a merged pull request can move its task to done. See Closed-loop agent delivery.

See what happened

Every run and flow event appears in Automation → Activity. See Automation areas: Flows, Agents, Activity and Catalog.