Scheduler Tasks
Use the scheduler tool to manage saved tasks. Always inspect existing tasks before creating, updating, deleting, or running one.
Actions
list_tasks: optional state[], type[], next_run_within, next_run_after
find_task_by_name: name
show_task: uuid
run_task: uuid, optional context
update_task: uuid, optional name, system_prompt, prompt, attachments[], schedule, timezone, plan[], state, dedicated_context
delete_task: uuid
create_scheduled_task: name, system_prompt, prompt, optional attachments[], schedule, timezone, dedicated_context
create_adhoc_task: name, system_prompt, prompt, optional attachments[], dedicated_context
create_planned_task: name, system_prompt, prompt, optional attachments[], plan[], dedicated_context
wait_for_task: uuid
Schedule Fields
Schedules use cron-like fields. Do not put ISO datetimes into schedule.
minute
hour
day
month
weekday
timezone
Use IANA timezones such as Europe/Rome. Omit timezone to use the current user timezone. Planned task datetimes go in plan, not schedule, and should be ISO strings such as 2026-05-09T18:25:00.
For one future reminder, prefer create_planned_task with:
{
"action": "create_planned_task",
"name": "drink water",
"prompt": "Remind the user to drink water.",
"plan": ["2026-05-11T09:15:00"],
"dedicated_context": true
}
For a recurring or cron-shaped scheduled task, use create_scheduled_task with:
{
"action": "create_scheduled_task",
"name": "weekday stretch",
"prompt": "Remind the user to stretch.",
"schedule": {
"minute": "15",
"hour": "9",
"day": "*",
"month": "*",
"weekday": "1-5",
"timezone": "Europe/Rome"
},
"dedicated_context": true
}
Safety
- Do not create recursive task prompts that schedule more tasks.
- Do not run a task just because it is scheduled; run only if the user asks.
- Created tasks use a dedicated context unless
dedicated_context is explicitly false.
- For destructive operations, identify the task by UUID after lookup.
Example
{
"tool_name": "scheduler",
"tool_args": {
"action": "find_task_by_name",
"name": "daily backup"
}
}
1---2name: scheduled-tasks3description: Create, edit, run or audit scheduled, planned and adhoc tasks; cron, timezones and reminders.4---56# Scheduler Tasks78Use the `scheduler` tool to manage saved tasks. Always inspect existing tasks before creating, updating, deleting, or running one.910## Actions1112- `list_tasks`: optional `state[]`, `type[]`, `next_run_within`, `next_run_after`13- `find_task_by_name`: `name`14- `show_task`: `uuid`15- `run_task`: `uuid`, optional `context`16- `update_task`: `uuid`, optional `name`, `system_prompt`, `prompt`, `attachments[]`, `schedule`, `timezone`, `plan[]`, `state`, `dedicated_context`17- `delete_task`: `uuid`18- `create_scheduled_task`: `name`, `system_prompt`, `prompt`, optional `attachments[]`, `schedule`, `timezone`, `dedicated_context`19- `create_adhoc_task`: `name`, `system_prompt`, `prompt`, optional `attachments[]`, `dedicated_context`20- `create_planned_task`: `name`, `system_prompt`, `prompt`, optional `attachments[]`, `plan[]`, `dedicated_context`21- `wait_for_task`: `uuid`2223## Schedule Fields2425Schedules use cron-like fields. Do not put ISO datetimes into `schedule`.2627- `minute`28- `hour`29- `day`30- `month`31- `weekday`32- `timezone`3334Use IANA timezones such as `Europe/Rome`. Omit timezone to use the current user timezone. Planned task datetimes go in `plan`, not `schedule`, and should be ISO strings such as `2026-05-09T18:25:00`.3536For one future reminder, prefer `create_planned_task` with:3738```json39{40 "action": "create_planned_task",41 "name": "drink water",42 "prompt": "Remind the user to drink water.",43 "plan": ["2026-05-11T09:15:00"],44 "dedicated_context": true45}46```4748For a recurring or cron-shaped scheduled task, use `create_scheduled_task` with:4950```json51{52 "action": "create_scheduled_task",53 "name": "weekday stretch",54 "prompt": "Remind the user to stretch.",55 "schedule": {56 "minute": "15",57 "hour": "9",58 "day": "*",59 "month": "*",60 "weekday": "1-5",61 "timezone": "Europe/Rome"62 },63 "dedicated_context": true64}65```6667## Safety6869- Do not create recursive task prompts that schedule more tasks.70- Do not run a task just because it is scheduled; run only if the user asks.71- Created tasks use a dedicated context unless `dedicated_context` is explicitly `false`.72- For destructive operations, identify the task by UUID after lookup.7374## Example7576```json77{78 "tool_name": "scheduler",79 "tool_args": {80 "action": "find_task_by_name",81 "name": "daily backup"82 }83}84```