Automations

Automations run a saved prompt repeatedly or on demand. Each automation owns its schedule and run history, so recurring work remains inspectable instead of disappearing into a notification stream.

Use an automation for a stable request such as reviewing a project each morning, collecting a periodic status, or running a monthly check. Keep the prompt specific enough that a later run can be understood without reconstructing the day it was created.

Create and schedule an automation

From Automations, create an automation with a name and prompt. You can optionally associate it with a project and choose an emoji for recognition in the list.

The shipped schedule types are:

• Daily, with selected weekdays and a time stored in UTC.
• Interval, for work repeated every configured number of hours.
• Monthly, for a selected day of the month and UTC time.
• Manual, which runs only when you choose Run now.

Review the displayed schedule before saving, especially when entering a UTC hour. The Automations list separates active and paused items and can filter by status. Pausing preserves the automation and its history but stops scheduled runs. Activating it resumes the schedule.

Run and operate it

Use Run now when you need an immediate run without changing the recurring schedule. The resulting run records that it was triggered manually; scheduled executions record their scheduled origin.

You can edit the automation's definition, pause or activate it, and delete it. Deletion is destructive: after confirmation, the automation and its task history are removed. Pause an automation when you need to retain its evidence.

The list shows the latest state, next scheduled time, associated project, and accumulated task count. Open an automation for the authoritative run history.

Read run provenance

The automation detail page presents recent activity as a run lane and a task history. Each run can report:

• whether it is pending, running, completed, failed, or skipped;
• whether it was started manually or by the schedule;
• start time, completion time, and duration when available;
• output for a completed run or the recorded error for a failed run;
• checks and proof references when the underlying task produced them.

Search the history to locate a result. Output can be copied or downloaded from the run detail. If a run created or used a chat, follow its thread link to review the prompt, conversation, and any work that followed.

Find the result

The automation's task history is the primary home for its results. Successful and failed runs remain side by side so that a missing report is not interpreted as a clean run.

Runs completed for the current day can also appear in For You under What ran while you were away. That section is a daily readback, not a replacement for the automation history. Use its thread link for context, or return to the automation detail when you need schedule provenance and the complete sequence of runs.