Skip to main content
Scheduled tasks are project-level triggers that enqueue work into room queues on a schedule. A scheduled task sends a message into a queue on a schedule. An agent or service in that room reads from the queue and does the work. The task lives at the project level even when it targets one room. For the queue and worker side of that workflow, see Queues and Scheduled Tasks.

​
Create a scheduled task

meshagent scheduled-task add \
  --room support \
  --queue support-jobs \
  --schedule "30 17 * * *" \
  --payload '{"prompt":"Generate the daily support summary."}'
This creates a scheduled task in the active project that enqueues work into the support-jobs queue in the support room. The payload can be any JSON value. For MeshAgent queue consumers, that includes the same structured prompt, content, and thread_id fields supported by meshagent room queue send. Example: 
meshagent scheduled-task add \
  --room support \
  --queue support-jobs \
  --schedule "0 * * * *" \
  --payload '{"thread_id":"/threads/support/{YYYY}/{MM}/{DD}/{HH}/summary.thread","prompt":[{"type":"file","url":"room:///prompts/hourly-summary.md"},{"type":"text","text":"Generate the hourly support summary."}]}'

​
Inspect and manage scheduled tasks

List tasks: 
meshagent scheduled-task list
meshagent scheduled-task list --room support
Update a task: 
meshagent scheduled-task update TASK_ID \
  --schedule "0 18 * * *" \
  --active
Delete a task: 
meshagent scheduled-task delete TASK_ID

​
Where to manage them

  • Use MeshAgent Studio when you want the main UI flow.
  • Use the CLI when you want quick setup or automation.
  • Use the REST API when you need programmatic provisioning.
If you want a recurring turn owned by one agent inside a service manifest, use agents[].heartbeat instead of a separate scheduled task.