Scheduled tasks
Schedule one-off or recurring work in EvoX Desktop. EvoX runs a task on this computer when it is due. Review its configuration, next run, and run history in Scheduled Tasks, or ask EvoX to draft a task in a conversation.
For a first task, use Scheduled Tasks in the sidebar: set the prompt, time, and scope, then use Run now to check the result. The demonstration below shows creation and editing in the Cowork form without creating or running a real task.
Use a schedule to summarize a project each morning, inspect a repository each week, or resume work at a specified time. EvoX runs it locally: closing the window does not stop it, but quitting EvoX, shutting down, or sleeping prevents execution. EvoX catches up one missed recurrence after it starts again.
Manage scheduled tasks
Open Scheduled Tasks from the left side of EvoX Desktop. The empty state offers New scheduled task plus Daily brief, Weekly review, and Follow-up monitor starters. Once tasks exist, you can inspect definitions and run history. Search, filters, and pagination appear only when the number and states of tasks make them useful.
Scheduled tasks
Tasks that run themselves. When it is time, a scheduled task returns to its conversation, runs one round, and adds the result to your conversation list.
No scheduled tasks yet
Start from a scenario
You can Run now, Pause or resume, Edit, or Delete a task, and open a result conversation from a run that has one. Pausing stops scheduled runs but does not prevent an explicit Run now. Running now does not advance the next scheduled time. Review a failure and its result before editing or retrying.
Execution mode and project directory are separate choices. Chat tasks do not bind a local directory; Cowork tasks support project selection; Code tasks require a valid workspace. A Code task works in the selected directory so define file ownership before running it alongside your work. Project membership does not grant extra file or external-service access.
Ask EvoX to create or update a task
Select New scheduled task in the manager and enter a name, prompt, cadence, and time, then check the execution mode and result conversation. The Cowork project form also offers project scope, a fresh or continuing conversation, and approval-free execution for this task only. That grant does not expand its workspace or allow desktop control.
You can also describe the work, timing, destination, and conversation behavior in a conversation. EvoX proposes a draft that you can edit, create, or decline. Nothing is scheduled without confirmation.
Every weekday at 09:00, check yesterday's progress in the Client Refresh project.
List completed work, blockers, and next steps in this conversation.
If there are no new blockers, keep the summary short. Do not send it externally.
Choose a time and creation entry
The entry points expose different time controls. The compact Cowork form does not include the full editor's advanced options:
| Entry | Time settings |
|---|---|
| Direct creation in a Cowork project | Daily or weekly; weekly requires a weekday |
| Full scheduled-task editor | Daily, weekly, fixed interval, one-off, custom Cron, or manual only |
| Confirmation card in a conversation | Daily, fixed interval, one-off, custom Cron, or manual only |
Manual only saves a task for Run now without scheduling automatic execution. The minimum fixed interval is 1 minute. The full editor places custom Cron and timezone overrides in Advanced options; daily and weekly forms display the timezone in use. For work across regions, specify an IANA zone such as Asia/Shanghai and check the saved next-run time instead of relying on “tomorrow at nine.”
After confirming, wait for the save result. If it fails, keep the draft and retry in the same form rather than creating several identically named tasks to find out whether one saved. The actual task and time in the manager establish the schedule; an AI statement that it is arranged does not.
Schedule in the current conversation
When a later run needs the context you are discussing, request the schedule in this conversation and choose to return here. A scheduled run then uses this conversation's context. If each run should be reviewed independently, choose a new conversation. The Cowork project form also offers fresh or continuing conversations. Returning to the same conversation continues the discussion; it does not retain every historical message as input forever.
Put durable source locations, output format, and stopping conditions in the task prompt. Avoid “do what we did last time”: recheck files, plugin connections, and required context for each run.
Test a scheduled task
Before enabling a schedule, run the same instructions manually in a normal conversation and check:
- The input sources, project directory, and target files are correct.
- The output is reviewable and failures explain what happened.
- Required plugins, network access, and file permissions work in this environment.
- Sending, publishing, deletion, and production changes have explicit approval boundaries.
After saving, use Run now for another check. Inspect the status and result conversation in Run history; “scheduled” does not mean the work will succeed. If a run fails or its directory moves, fix the source or permission before retrying.
Diagnose failures and recover
First distinguish an unsaved definition, unfinished work, and an undelivered result:
| What you see | Next action |
|---|---|
| Creating or editing reports a save failure | Review the error and retry in the original form; inspect the manager to confirm the saved state |
| Pausing or deleting reports an error | The task remains; confirm the action succeeded before assuming future runs have stopped |
| Project directory, connected folders, or working rules changed | Review the current project scope before Run now; fix scope synchronization errors instead of executing with old access |
| A confirmation card asks you to send a message first | Send a normal message to establish the current conversation, then retry the card |
| A run ended without the requested deliverable | Open its result conversation and inspect sources, errors, and actual files before correcting the prompt or permissions |
| A summary exists but says the push was not sent | Check recipients, connection, and the delivery error; resolve delivery rather than repeatedly rerunning the entire task |
Verify generation and delivery separately
Cowork scheduled summaries can push results to Feishu. Saving a fixed recipient list with approval for automatic delivery authorizes subsequent results to that list. Older configurations without this approval still require confirmation each time. Confirm a new recipient or a wider sending scope explicitly; a line in the prompt saying “also send it to someone else” does not establish that authorization.
Check both the deliverable and the delivery record. Successful generation does not prove receipt, and a delivery failure does not require generating the content again. Successful recipients are deduplicated by run; fix failed deliveries and check their outcomes.
Clean up results
Recurring tasks can produce many conversations, run records, and output files. Review tasks you no longer need, pause or delete their definitions, and organize generated files according to your project rules. Deleting a schedule does not undo previous file changes or automatically remove a workspace it used. Preserve results you need before cleanup.
Clean up a Code task workspace
EvoX does not create a Git worktree merely because you created a scheduled task. A scheduled Code task works directly in the workspace saved in its configuration.
If that directory is an isolated task worktree created by EvoX in Code mode, first disable or delete the related schedule and preserve or commit any changes. Then open the Isolated task worktrees panel in Code mode and choose Clean up task worktree. Cleanup removes the managed worktree and, when Git allows it, its EvoX task branch. EvoX warns before force-removing a worktree with uncommitted changes.
Do not clean up a directory while an enabled Code schedule still points to it. Change the schedule's workspace or disable/delete the task first, otherwise the next run fails because its workspace is missing.
Permissions and safety
An unattended task retains the permissions of its execution mode. Confirming a schedule is not a blanket approval for every future tool call; an operation that needs interactive approval fails with a recorded reason when nobody can approve it. If a Cowork task offers a per-task unattended-approval switch, it applies only to that task's scheduled runs and does not enable desktop control or expand its workspace boundary.
Grant only the directories and tools needed. App shutdown, an unavailable project directory, expired credentials, or a disconnected plugin can make a run fail. See Permissions for the general access model.
Examples
Produce a regular project brief
Every day at 09:00, summarize this project's new task results from the past day.
Use Completed / Needs attention / Next steps and link to source conversations.
If nothing changed, say so rather than inferring progress.
Review recent repository changes
Every Friday at 17:00, inspect this repository's changes and relevant tests.
Produce a traceable brief with failures and evidence.
Do not commit, push, or change production configuration automatically.
Use an enabled skill for repeat work
Every Monday, check the project's meeting notes and use the currently enabled
summary skill to extract action items and owners. If the skill or source is
unavailable, record why; do not switch to an unapproved external service.
EvoX Docs · Features · Workflows