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.

A demonstration-video slot is reserved. The existing daily-brief clip is a workflow sample with an outdated UI and will be replaced with a recording of the current client.

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.

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 may select a project; Code tasks require a valid workspace. A Code task works in the selected directory and may change files you are using. 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, then enter a name, prompt, cadence, time, and project scope. You can choose a fresh conversation for every run or continue the previous one, and grant approval-free execution only to this task. 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.

The current Cowork form offers daily and weekly choices, including a weekday for weekly tasks. Versions with the full scheduled-task editor can also represent one-off, fixed-interval, or custom Cron schedules. The interface only exposes options the current client and kernel can execute.

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. Supported Cowork versions can also choose between a fresh conversation per run and continuing an existing one.

Put durable source locations, output format, and stopping conditions in the task prompt. Avoid “do what we did last time”: files, plugin connections, and conversation context may have changed by the next 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.

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