Automations
An Automation saves instructions and a model choice for work you repeat. Each Run starts a fresh Session with those instructions as its first message. It does not resume an existing Session.
What an Automation saves
Section titled “What an Automation saves”| Part | What it controls |
|---|---|
| Name | The name shown in the Automations list and run menus. |
| Instructions | The new Session’s first message. Use / to reference Commands and Skills, or @ to reference files. |
| Trigger | What can start it automatically: None, Columns, or Schedule. |
| Runtime → Model | Project default, a named default tier, or an exact model and reasoning level. |
| Scope | This project or All projects. Schedules require This project. |
Each Run records the Automation’s name and the model and reasoning that started its Session. Run history links back to that Session.
Choose a Trigger
Section titled “Choose a Trigger”You can run any saved Automation by hand, whatever its Trigger.
This adds no automatic start. See Create a manual Automation.
Columns
Section titled “Columns”Choose the board columns that offer the Automation. Each column can arm one of its offered Automations to run when a ticket arrives. See Arm a column Automation.
Schedule
Section titled “Schedule”Start a project-level Board Session at a recurring time. See Schedule an Automation for time zones and missed occurrences.
Automatic trigger settings
Section titled “Automatic trigger settings”For a column or schedule Trigger, turn on Automatic triggers in the Automation’s Trigger section. It is off by default and applies only to this Mac. A column Trigger also needs an armed column. You can still run the Automation by hand while automatic starts are off.