Skip to main content
Automations let you save prompts that run on a schedule. They are available to every workspace. Each automation stores one saved prompt — the instruction that daoco runs on every scheduled tick. That prompt is the source of truth for what the automation does.

​
Create a scheduled prompt

1

Open Automations

Choose Automations from the sidebar.
2

Create a new automation

Add a name, saved prompt, and schedule. Write instructions that can run without extra chat context.
3

Preview the schedule

Check the interpreted schedule and next run times before saving.
4

Choose Improve prompt (optional)

Turn on Improve prompt when you want completed runs to refine the saved prompt in place when they find a durable lesson.
5

Save active or paused

Active automations can run when due. Paused automations keep their settings but do not run.

​
Improve prompt

When Improve prompt is enabled, a successful automation run may update only the automation’s saved prompt — not its name, schedule, timezone, or active/paused status. Use this when you want recurring runs to tighten instructions over time, such as preferred report format, source priorities, or review habits.
Prompt self-improvement is not permission. It cannot authorize publishing, integration writes, deletions, or approval bypasses. Approval preferences still apply to every sensitive action.
When Improve prompt is off, completed runs cannot change the saved prompt.

​
Review run history

Open an automation’s run history to see:
  • Run status, timing, and errors.
  • Approval audit events when an action was auto-allowed, blocked, or required manual approval.
  • Legacy workflow memory references on older runs only.
If no approval policy allows bypass, the automation pauses behind the normal approval gate until someone approves or denies the pending action. Use failed or paused runs to refine the saved prompt or schedule.

​
Pause, resume, or archive

  • Pause an automation when you want to keep it but stop future runs.
  • Resume it when the schedule should run again.
  • Archive it when it is no longer needed.

​
Workflow memory (legacy)

Older automations may show attached workflow memory in run history. The workflow memory library UI was removed in favor of the saved prompt plus optional Improve prompt self-improvement. New automations should put durable operating instructions directly in the saved prompt.