|
| 1 | +# Create a scheduled task |
| 2 | + |
| 3 | +Ask Agent Zero to do something on a schedule, then come back to its results. |
| 4 | +You can create a task in **Scheduled Tasks** or describe what you want in a |
| 5 | +normal chat. Both methods save it in the same task list. |
| 6 | + |
| 7 | +This guide uses two examples: Sunday dinner ideas created with the form, and |
| 8 | +a weekday writing warm-up created through chat. |
| 9 | + |
| 10 | +- [Open Scheduled Tasks](#open-scheduled-tasks) |
| 11 | +- [Create a task with the form](#create-a-task-with-the-form) |
| 12 | +- [Create a task through chat](#create-a-task-through-chat) |
| 13 | +- [Find the task and its conversation](#find-the-task-and-its-conversation) |
| 14 | +- [Run, pause, edit, or delete a task](#run-pause-edit-or-delete-a-task) |
| 15 | +- [Check timing and missed runs](#check-timing-and-missed-runs) |
| 16 | + |
| 17 | +## Open Scheduled Tasks |
| 18 | + |
| 19 | +Open **More options**, the dropdown arrow at the top of the sidebar, then |
| 20 | +select **Scheduled Tasks**. The modal lists saved tasks and their states. |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +Select **New Task** to open the creation form. |
| 25 | + |
| 26 | +## Create a task with the form |
| 27 | + |
| 28 | +Let's set up dinner ideas for Sunday at 18:00. Fill in these fields: |
| 29 | + |
| 30 | +| Field | What to enter | |
| 31 | +| --- | --- | |
| 32 | +| **Task Name** | `Sunday meal ideas`, or another name you will recognize. | |
| 33 | +| **Type** | **Scheduled (Cron)** for a repeating task. | |
| 34 | +| **Project** | **No project** for this example. Choose a project if the task needs its files, instructions, or connections. The form initially uses the active chat's project. | |
| 35 | +| **State** | **Idle (ready to run)**. Choose **Disabled** if you want to save it without enabling scheduled runs yet. | |
| 36 | +| **Schedule** | Minute `0`, Hour `18`, Day `*`, Month `*`, Weekday `0`. | |
| 37 | +| **System Prompt** | Optional guidance for how to respond. For example: “Keep suggestions practical and use everyday ingredients.” | |
| 38 | +| **User Prompt** | The work to do each time. Use the dinner request below. | |
| 39 | +| **Attachments** | Optional file paths inside Agent Zero or URLs, one per line. Leave empty for this example. | |
| 40 | + |
| 41 | +For **User Prompt**, enter: |
| 42 | + |
| 43 | +> Suggest three easy vegetarian dinners for two for the coming week. Keep each |
| 44 | +> recipe under 30 minutes and give me one combined shopping list. |
| 45 | +
|
| 46 | +Put the timing in **Schedule** and the work in **User Prompt**. The task's |
| 47 | +prompt should ask for the dinners, not ask Agent Zero to create another task. |
| 48 | +Use **Expand** beside either prompt if you need more room to write. |
| 49 | + |
| 50 | + |
| 51 | + |
| 52 | +### Read the five schedule fields |
| 53 | + |
| 54 | +The fields run from left to right: **Minute, Hour, Day, Month, Weekday**. |
| 55 | +`*` means every value in that field. Hours use the 24-hour clock, and weekday |
| 56 | +`0` means Sunday; `1` through `6` mean Monday through Saturday. |
| 57 | + |
| 58 | +| When | Minute | Hour | Day | Month | Weekday | |
| 59 | +| --- | --- | --- | --- | --- | --- | |
| 60 | +| Every day at 09:00 | `0` | `9` | `*` | `*` | `*` | |
| 61 | +| Weekdays at 08:30 | `30` | `8` | `*` | `*` | `1-5` | |
| 62 | +| Sundays at 18:00 | `0` | `18` | `*` | `*` | `0` | |
| 63 | + |
| 64 | +**Five asterisks means every minute.** Replace the fields before saving. |
| 65 | +New tasks use the timezone in **Settings → Agent → Locale**. With **Automatic |
| 66 | +(browser)** selected, that comes from your browser. |
| 67 | + |
| 68 | +For a one-time job, choose **Planned (Specific Times)**, pick the date and time, |
| 69 | +and select **Add Time** before saving. You can add more than one date. |
| 70 | +**Ad-hoc (Manual)** saves a task you run on demand, without a repeating schedule. |
| 71 | + |
| 72 | +### Save and check it |
| 73 | + |
| 74 | +Select **Save**. The form closes and **Sunday meal ideas** appears in the list. |
| 75 | +**Idle** means ready for its next scheduled run; saving it does not run it |
| 76 | +immediately. |
| 77 | + |
| 78 | + |
| 79 | + |
| 80 | +Click its row to inspect the saved details. To try it now, select the triangle |
| 81 | +button, **Run Task**, or **Run** inside Task Details. Open its conversation from |
| 82 | +the sidebar **Tasks** section to watch the work and read the result. |
| 83 | + |
| 84 | +## Create a task through chat |
| 85 | + |
| 86 | +You can skip the form and ask in your own words. For example: |
| 87 | + |
| 88 | +> Every weekday at 8:30 in the morning, give me a quick writing warm-up: a fun |
| 89 | +> prompt I can finish in ten minutes and one tip to help me start. Keep these |
| 90 | +> in their own chat so I can find them easily. |
| 91 | +
|
| 92 | +Send this in a normal chat. If you want the task to belong to a project, open |
| 93 | +a chat in that project first. Mention a timezone if the time should be |
| 94 | +different from your Agent Zero setting. |
| 95 | + |
| 96 | + |
| 97 | + |
| 98 | +Wait for Agent Zero to confirm that it created the task. Then open |
| 99 | +**More options → Scheduled Tasks** and find **Writing warm-up**. Click its row |
| 100 | +to check the saved schedule and instructions. In this example, the schedule is |
| 101 | +`30 8 * * 1-5`: weekdays at 08:30. |
| 102 | + |
| 103 | + |
| 104 | + |
| 105 | +The wording of the confirmation can vary. The saved task is what tells you |
| 106 | +the automation exists. If Agent Zero asks a follow-up question, answer it and |
| 107 | +check the list once creation is confirmed. |
| 108 | + |
| 109 | +## Find the task and its conversation |
| 110 | + |
| 111 | +**Scheduled Tasks** is the complete list. Use its **Type** and **State** filters |
| 112 | +to narrow it down. If a task seems missing, return to **All Types** and |
| 113 | +**All States**. |
| 114 | + |
| 115 | +Tasks with a **dedicated chat** also appear under **Tasks** in the sidebar. |
| 116 | +Expand that section if it is collapsed, then select a task's name to open its |
| 117 | +conversation. Both the form and the agent normally create dedicated chats; |
| 118 | +each task's results stay together across runs. |
| 119 | + |
| 120 | + |
| 121 | + |
| 122 | +If you ask Agent Zero to run a task in the current conversation instead, its |
| 123 | +results stay in that shared chat under **Chats**. The task still appears in |
| 124 | +**Scheduled Tasks**, but it does not get a separate sidebar task entry. |
| 125 | + |
| 126 | +Plugin tasks such as [A0Cleaner](cleaner.md) can also appear in Scheduled Tasks. |
| 127 | +They run the plugin's operation and do not need a task conversation. |
| 128 | + |
| 129 | +## Run, pause, edit, or delete a task |
| 130 | + |
| 131 | +Click a task's row for **Task Details**, including its schedule, **Last Run**, |
| 132 | +**Last Result**, and saved prompts. For the ongoing conversation, select its |
| 133 | +sidebar task entry. |
| 134 | + |
| 135 | +| What you want | What to use | |
| 136 | +| --- | --- | |
| 137 | +| Run it now or run it again | **Run Task** (triangle) in the list, or **Run** in Task Details. A disabled task must be enabled first. | |
| 138 | +| Pause the agent's current work | Open its conversation and select **Pause Agent**. Use **Resume Agent** to continue. | |
| 139 | +| Stop future scheduled runs | **Edit Task** (pencil), choose **Disabled**, then **Save**. This does not cancel work already running. | |
| 140 | +| Enable it again | Edit its state to **Idle** and save. | |
| 141 | +| Change the prompt or schedule | **Edit Task**, update the fields, then **Save**. The task's type and project cannot be changed in this editor. | |
| 142 | +| Make an interrupted task ready again | **Reset State** (circular arrow) returns it to **Idle**. It does not run the task or clear its conversation. | |
| 143 | +| Delete it | **Delete Task** (trash), then click the confirmation checkmark. Deleting a dedicated task also removes its task chat. | |
| 144 | +| Clear its conversation | **Clear task chat** in the sidebar. This erases the task's chat history while keeping its definition. It is not needed for an ordinary rerun. | |
| 145 | + |
| 146 | +Scheduled runs currently do not show the regular **Stop agent** button. |
| 147 | +Use **Pause Agent** when you need to interrupt the agent without deleting its |
| 148 | +conversation. Resetting a state is not a way to stop work that is still running. |
| 149 | + |
| 150 | +The state badges help you see what needs attention: **Idle** is ready, |
| 151 | +**Running** is executing, **Disabled** is switched off, and **Error** needs a |
| 152 | +look at the result or chat. Use **Run Task** to start work; selecting a state |
| 153 | +label does not start an agent run. |
| 154 | + |
| 155 | +## Check timing and missed runs |
| 156 | + |
| 157 | +Agent Zero needs to be running to do the work. If a recurring task misses its |
| 158 | +time while the container is off, an enabled, idle task catches up once after |
| 159 | +startup. Several missed occurrences become one run, then the normal schedule |
| 160 | +resumes. Disabled or failed tasks do not catch up automatically, and a run |
| 161 | +interrupted by shutdown needs your attention. |
| 162 | + |
| 163 | +Changing a recurring schedule or re-enabling a task starts its timing from |
| 164 | +that change. Existing tasks keep their saved timezone; changing Locale does |
| 165 | +not rewrite them. You can ask in chat, for example, “Change my writing warm-up |
| 166 | +to 8:30 London time.” |
| 167 | + |
| 168 | +Try the work once before relying on it unattended. A scheduled inbox summary |
| 169 | +still needs a working email connection, and a task that uses an AI model uses |
| 170 | +your normal model account and settings. Its results appear in Agent Zero; |
| 171 | +delivery to email or another app needs to be part of the request and configured. |
0 commit comments