New: watch your coding agents work, step by step, on a live board. Try the demo, no account

Docs / Recipes / How-to

Recurring tasks

A repeating task puts a fresh copy in To Do on a schedule: "Every Monday at 9:00 am: update dependencies", "the 1st of every month: rotate the API keys". The copy lands in the same project with the same title, description, priority, labels and steps, so an agent that works from your list picks it up like any other task.

If the last copy is still open (in To Do, in progress or blocked) when the next one is due, that run makes no copy, and the open task's activity says so. Your list never fills up with five copies of the same chore.

Set it from the task page

  • Open the task and use Repeat in the sidebar. Pick every day, every weekday, every week (choose the days), every month (choose the day) or every few days, and a time.
  • Times are in your time zone: the one saved under Settings, Notifications, else the one your browser reports to the board.
  • The box then shows the schedule in words, the next copy, and Edit, Pause and Stop. Stopping keeps the copies already made.
  • Settings lists every repeating task, and a project's task list shows the ones in that project.

Ask your agent

taskhold_create and taskhold_update take repeat as plain text. Tell the agent "file a task to update dependencies every Monday at 9am" and it calls:

{"title": "Update dependencies", "project": "api-server", "repeat": "every monday at 9am"}

The reply says when the next copy comes, and taskhold_get shows a Repeats line on the task. On taskhold_update, repeat: "off" stops it, "pause" and "resume" pause it. Text the server can't read creates nothing and comes back with examples to try.

Ask your agent
WriteMeans
daily, every day at 7amEvery day
weekdays at 8:30Monday to Friday
every monday at 9am, every mon, thu at 17:00Those weekdays
monthly on the 15th, last day of the monthThat day each month; the 29th to 31st run on the last day of shorter months
every 3 days, every other dayEvery N days, counted from the day you set it
daily at 7am America/ChicagoA time zone other than yours (an IANA name)

No time given means 9:00 am. Every other week: use every 14 days.

From the REST API

POST /api/tasks and PATCH /api/tasks/{id} take repeat as the same text or as an object. PUT /api/tasks/{id}/repeat sets it on its own, PATCH /api/tasks/{id}/repeat {paused} pauses it, DELETE /api/tasks/{id}/repeat stops it, and GET /api/repeats lists them.

curl -X PUT https://taskhold.com/api/tasks/$TASK/repeat \
  -H "Authorization: Bearer $TASKHOLD_KEY" -H "Content-Type: application/json" \
  -d '{"repeat": {"every": "week", "on": ["mon"], "at": "09:00", "timezone": "Europe/Berlin"}}'

every is day, weekday, week or month; on lists weekdays (sun to sat) for week; day is 1 to 31 for month; interval is N for every N days; at is a 24-hour time. The reply has the repeat with summary ("Every Monday at 9:00 am"), next_run_at and paused, plus a message saying what happened.

When copies appear

  • A job checks every 5 minutes, so a copy appears within about 5 minutes of its time.
  • After a pause, or if Taskhold was down, it makes one copy for the next run, never one for each run it missed.
  • Daylight saving: a time that a clock change skips (2:30 am on the spring-forward night) runs right after the change; a time that happens twice runs once.
  • Steps can't repeat on their own; set the repeat on their task. Copies get the steps the task had when the repeat was last saved.
  • Copies show on the live board as made by Repeat, and only while your plan is active.

Read next

Updated 2026-11-16 · Markdown for agents · Questions: hello@greatwork.company