Automations
Understand Tejus's scheduled-work surface, then follow the detailed workflow guide.
Automations run a defined objective on a schedule, for work that does not fit a single interactive thread.
Automations
Open Automations in the app rail (or search for Go to Automations with Ctrl+K). The list groups your automations into Active and Paused, and New automation creates one. You can also type /automation in a chat composer to turn the current prompt into a scheduled automation.
Each automation's page shows its status, a Run now button, Pause / Resume and Delete, and sections for Status, Details, Memory, and Previous runs (the run history). Settings such as the schedule, model, mode, notifications, Stop when, On failure, and Max iterations can be edited in place. Turns that an automation started are marked in the thread's transcript.
Use an automation when the objective, schedule, environment, verification, and stop condition can be reviewed before the first run. Scheduled work still uses real providers and environments, so its output requires the same diff and test review as an interactive thread.
Give scheduled work explicit authority, deliverables, verification, and completion criteria before letting it continue unattended.