Recurring tasks

A recurring task runs automatically on a schedule you define, then keeps a history of every run. Under the hood the schedule is a cron expression, but you don't have to write one by hand — the scheduler builds it for you and shows the next run before you commit.

Schedules fire in the timezone you choose, which defaults to the agent's timezone. So "9am" means 9am in that zone, regardless of where the machine runs.

Create a recurring task

From Scheduled tasks, click New scheduled task to open the full scheduler (or tick Recurring task in the quick New task dialog).

1. Give the task a title and write the instructions that run on every trigger.
2. Pick a frequency: Hourly, Daily, Weekly, Monthly, or Custom.
3. Set the time, and the days for weekly/monthly schedules.
4. Choose the agent and confirm the timezone.
5. Review the live cron expression and the First run preview, then click Create task.

The task starts on its schedule as soon as it's created.

From a chat

Already got a chat that does the job? Turn it into a schedule instead of retyping it:

1. In the chat header, open the ⋯ menu and choose Turn into a recurring task.
2. Check the Name (the chat's title) and the Instructions — they're seeded from your first real request in the chat, so edit them to read as standing instructions for every run.
3. Pick when it Runs — a preset such as Every day at 9am (the default), Every weekday at 9am, or Every Monday at 9am, or Custom to type a cron expression.
4. Click Create task.

The task runs on the same agent as the chat, in that agent's timezone, and opens in Scheduled tasks so you can review it. A chat whose agent has been deleted can't be turned into a task — start a new chat with an agent first.

Schedule limits by plan

The available frequencies depend on your workspace plan:

In the quick New task dialog, frequencies finer than your plan allows are hidden from the picker. Elsewhere, a schedule that runs more often than your plan allows is refused when you save it. See Plans.

Manage a schedule

Open a recurring task to see its schedule card (cadence, time, days, agent, timezone, cron, and next run) and its run history. Schedules are described in plain words — for example Every Hour, Every Hour at :15, Every 6 hours, or Weekdays for a Monday–Friday schedule. From here you can:

• Run now — trigger an extra run immediately, on top of the schedule.
• Pause / resume — flip the toggle; a paused schedule stops firing until you resume it.
• Edit schedule — change the cron expression or timezone (presets or a custom expression).
• Edit instructions — changes apply from the next run.
• Open a run — jump into the chat for any past execution to see what the agent did.
• Delete a run — remove an entry from the run history.

Schedules the agent creates itself

An agent can also put work on its own clock. Mid-task it might conclude "the invoice won't clear until Thursday" or "this report is worth running every Monday" — instead of only saying so, it can book the follow-up itself, either as a recurring schedule or as a one-time run at a future date and time.

These are ordinary tasks. They appear in Scheduled tasks alongside the ones you create, marked as scheduled by the agent, and you stay in control of them: a recurring one can be paused, edited, run now or deleted like any other, and a one-time run can be paused (which holds it until you resume it) or deleted. Nothing runs on a separate clock you can't see.

You can also manage them just by asking the agent — for example "move my Monday report to 8am", "pause the daily inbox summary", or "turn it back on". The agent can:

• List its schedules, including the ones you created.
• Edit a schedule it created — its instructions, title, timing (a new cron or time of day for a recurring schedule, a new date and time for a one-time run) or timezone. A recurring schedule stays recurring and a one-time run stays one-time; to switch, it cancels and books a new one.
• Pause and resume a schedule it created. A paused one-time run whose time passes while it's paused isn't fired the moment it resumes — the agent moves it to a new time first.
• Cancel a schedule it created.

They also play by the same rules as your own:

• They count against your workspace's monthly task quota.
• They obey your workspace plan's minimum frequency — an agent can't schedule work more often than your plan allows, whether it's creating, editing or resuming a schedule.
• Each agent can hold at most 25 schedules of its own at a time.