Automations

Automations send a task prompt on a schedule. Use them for a recurring project check, a summary, or a one-time follow-up. The Automation plugin must be enabled and Wuu must be running on an awake machine; this is not a hosted scheduler.

Create a task

1. Open Automations and choose the workspace. This selects the task’s workspace without changing your open conversation.
2. Choose New automation. Enter a name and clear instructions.
3. Under Runs in, choose New chat each run or an existing chat.
4. Set a daily, weekday, weekly, or custom schedule, and turn on Run once for a single run. More settings contains timezone and Isolated run.
5. Choose Create. Later edits require Save changes.

Include limits in the prompt, not just the desired action:

Summarize changes in this project's main branch since yesterday. Identify failed
checks if their results are available. Do not edit files or publish anything.

Choose where it runs

A new-chat task creates a visible conversation for each run. Runs can overlap. Enable Isolated run for a separate Git worktree based on the workspace’s current HEAD; uncommitted changes are not copied into it.

An existing-chat task continues that conversation’s context and workspace. If it is busy, the message queues behind its current work. This mode cannot create a new worktree. The agent’s cron tool calls these modes new_thread and thread_heartbeat.

Schedule and missed triggers

Custom schedules use five-field cron expressions. 0 9 * * 1-5 means 09:00 on weekdays in the selected timezone. Use IANA timezone names such as Asia/Shanghai; the desktop initially selects the system timezone.

The weekday field accepts 0–7: 0 and 7 both mean Sunday, and 1–6 mean Monday through Saturday. Lists and ranges keep their numeric step selection before interpreting Sunday: 6,7 and 6-7 select the weekend, 5-7/2 selects Friday and Sunday, but 6-7/2 selects only Saturday. Including both 0 and 7 does not create an extra Sunday occurrence.

Older versions could save a next-run time that skipped a selected Sunday. Restarting Wuu preserves that stored time. After upgrading, open an affected task, edit a field such as its name, then choose Save changes to recalculate immediately. The cron expression can stay unchanged; Save changes is disabled until the task is edited.

Without that update, an active recurring task recalculates after dispatch at its saved deadline; a one-shot task keeps its old deadline. Paused tasks stay paused after upgrading or saving; resume them explicitly when ready. Missed Sundays are not replayed.

The plugin checks due tasks about every 15 seconds, so a schedule is not a promise of an exact start second. After downtime, an overdue one-shot task is dispatched once. An overdue recurring task is dispatched once and then scheduled forward from the current time, rather than replaying every missed occurrence.

A one-shot task leaves the schedule when dispatched, even if execution later fails. Check its run record for the outcome; it is not automatically retried as a new one-shot task.

Manage tasks and results

The sidebar follows the workspace selected on the page. Running now shows starting, running, and queued executions; Up next lists enabled schedules by trigger time, with each task’s timezone. Select a row to open its details, including a one-shot task that has already left the schedule. The lists refresh about every 15 seconds while the window is visible, when returning to it, and after edits. A refresh failure is shown alongside the last available data.

Scheduled tasks are listed by next run. The switch on a task’s row, or Enabled in its editor, pauses and resumes future triggers; a paused task keeps its place. Delete removes the schedule, not conversations it already created, and does not stop work already running. Stop that work from its conversation. Closing the editor or selecting another task discards unsaved edits.

The detail panel shows recent runs and their errors, and a task whose last run failed is marked in the list. A one-shot run remains in the catalog after it leaves the schedule: Recent runs lists retained snapshots that are still starting, queued, running, failed, interrupted, or uncertain, and Completed lists successful ones. A successful recurring run does not complete its schedule. A workspace retains up to 100 tasks and 500 run records.

If a run is missing, check that Wuu was awake and running, the plugin was enabled, the task was active, and the selected workspace and target chat still exist. Then check its timezone, next run, and errors. Provider access, quotas, network failures, and permissions can all prevent execution.

For CI or a scheduler outside Wuu, use wuu exec.