Let an agent run on a clock.
A scheduled task starts one of your agents on a cron schedule — a morning report, a nightly check, a weekly digest. Each run is an ordinary conversation you can open, continue and share, and it uses the same account, environment and sandbox as a chat you start yourself.
Create a task
Open Settings → Scheduled tasks → Add task. Every user has this page and sees only their own tasks.
| Field | What to put |
|---|---|
| Agent | One of your agents. Required. |
| Model | Optional. Empty follows the agent's default model. |
| Cron expression | Five fields, see below. Required. |
| Timezone | An IANA name such as Asia/Shanghai or America/New_York. Starts as your browser's; empty means UTC. |
| Description | Optional note for yourself. |
| Task content | The prompt. It becomes the first user message of each run's conversation. Required, up to 64 KB. |
| Enabled | Untick to pause: the schedule and history stay, no new runs start. |
| Send notification | Push the result through your Bark or PushDeer channel (Notifications). |
| Send result to bot | Also post the answer into one of the agent's IM threads (below). |
Save task. The list shows each task's Next run and Last run, and Open chat takes you to its conversation.
Cron syntax
Standard five-field POSIX cron: minute hour day-of-month month day-of-week, evaluated in the task's timezone.
| Expression | Runs |
|---|---|
0 * * * * | every hour, on the hour |
0 9 * * 1-5 | weekdays at 09:00 (the default for a new task) |
0 18 * * * | every day at 18:00 |
*/15 9-18 * * 1-5 | every 15 minutes during office hours |
0 8 1 * * | 08:00 on the first of each month |
What a run does
- It opens a new conversation for the agent, titled Scheduled · plus the start of the prompt, in the agent's working directory.
- It waits for a free slot on the account like any other task — up to 30 minutes.
- If the previous run of the same task is still going, the new one is skipped (not stacked) and the reason shows as the task's last error.
- Missed runs while the server was down: on start-up only the most recent one is caught up, and only if it is under 72 hours old.
- Nothing starts while an admin has paused new tasks for maintenance.
Deliver results to IM
With Send result to bot on, the answer is also posted into
an IM thread of the agent, prefixed ⏰ DayMug 定时任务:.
Deliver through picks the thread; the default is the
agent's most recent one. The agent needs a thread first — mention
the bot once in Slack, 飞书, Telegram or 微信 and it appears in the
list. Bark / PushDeer stay quiet for that run, and follow-ups you
type in the web conversation are not relayed to IM.
Paused tasks
A task stops starting runs when:
- You paused it — it shows Paused; tick Enabled again.
- Its agent is gone — archived, deleted or moved to another owner. DayMug disables the task the next time it would fire and says so on the task; create a new task for an existing agent.
- Its schedule no longer parses — the expression or timezone is invalid. Correct it and enable the task again.
Enabling a task again clears the reason and the last error.
Tasks are created only from this page. Asking an agent in chat to “run this every morning” won't create one.