Scheduled tasks run recurring work in the background. Everything is created and tracked from Scheduled in the icon rail, which also lists past runs and marks unread ones. Tasks can fire on a clock or from webhook events.
A task set to Local runs against a project on your computer, so the desktop app must be open when it is due. Cloud tasks also work from the desktop app.
Manage scheduled tasks on the web
Cloud tasks run in a sandbox on ZeroTwo's servers and fire even when your computer is off. They can target a new chat or a GitHub repository. Nothing persists on a local machine between runs, so keep durable instructions in the prompt itself, try the prompt in a normal chat first, and tune it over the first few runs.
Trigger tasks from events
A task can start from an incoming webhook instead of a clock. The providers are GitHub, Linear, Sentry, PagerDuty, a generic Webhook, and Firecrawl Monitor for watching pages. For the webhook providers, ZeroTwo shows a webhook URL that you paste into the other service; nothing runs until that service is pointed at it. The URL carries a token, so treat it like a credential. A signing secret is optional, and which side creates it depends on the provider. Filters also vary, because each provider only sends some fields.
- GitHub: repository webhook events such as
workflow_runorissues.opened, with filters for events, repository and, for build results, branch. ZeroTwo creates the signing secret, and you paste it into GitHub's webhook form. - Webhook: any sender that can POST to the URL, with an optional comma-separated events filter. ZeroTwo creates the signing secret here too.
- Linear and Sentry: an events filter taking the action names those services send (for example
createorupdatefor Linear,createdorresolvedfor Sentry). These services generate their own signing secret, so the trigger stays unsigned until you paste that secret into ZeroTwo. - PagerDuty: every delivery wakes the task, because there is nothing to filter on. PagerDuty also generates its own signing secret, which you can paste into ZeroTwo.
- Firecrawl Monitor: ZeroTwo sets this up for you, so there is no URL to paste. It runs when a watched page, website or web search changes, checked on a cadence from every 15 minutes to daily.
The trigger belongs to one provider, chosen when the task is created. To listen for a different event, create a new task. There are no Gmail or Slack triggers.
Manage scheduled tasks
The Scheduled list can be searched and filtered by All, Active or Paused. Use Create with ZeroTwo to describe the job in chat, or Set up manually to open the editor. In the editor choose where the task runs (Local or Cloud), whether each run opens a New chat or continues an Existing chat, the model and reasoning effort, and the cadence: Doesn't repeat, Interval in minutes or hours, Daily, Weekly, Monthly or Annually. A task can run at most once a minute. For local tasks in a Git project you can run in place or in a separate worktree, which keeps unfinished work safe. Run now starts a task immediately.
Scheduled runs have nobody to approve actions, so they never ask. Write prompts that stay narrowly scoped. A connector the task uses must already be allowed to run: if one is missing permission, the schedule says which connector it needs and links to where you can allow it.
Runs, notices and unread marks
A thread created by a schedule shows a clock marker in the sidebar, and the run's prompt is labeled "Sent by scheduled task". Selecting that label opens the task. Scheduled pages show an unread dot when a task has new runs, and it stays in sync across devices. A task that fails notifies you the first time it fails. If your plan or credits do not allow a run, no empty thread is left behind and the schedule says why it skipped. When that happens 3 times in a row, ZeroTwo pauses the task, sends you one notification, and the task says why it was paused. Press Resume to start it again. A local run that was left overdue reads "Missed run on …".
A one-time task starts at the next 9:00 AM that is still ahead of you. Picking a time that has already passed shows "That time has already passed" and blocks Create.
Ask ZeroTwo to create or update scheduled tasks
Describe the job, the timing, and whether runs should return to the current chat. ZeroTwo drafts the prompt and schedule, and you can ask it to revise either later.
Schedule a task inside a chat
Choose Existing chat as the run target to revisit a chat with its context on a schedule. This suits long operations, periodic source checks and ongoing triage; pick a new chat when runs should be independent. Make the prompt say what to do, what is worth reporting, and when to stop.
Test scheduled tasks
Run the prompt in a normal chat first to check scope, model and output, then use Run now on the task and review the early runs.
Worktree cleanup for scheduled tasks
Frequent worktree runs accumulate. In Settings > Worktrees, Automatically delete old worktrees keeps only a set number of managed worktrees.
Examples
Stay up-to-date with your project
A local task summarizes the last day of commits on origin/main as a briefing organized by workstream, with PR links and no commit hashes.