Create a scheduled task with clear scope

Open Scheduled tasks, select Admin tasks, then Create task. Service tasks use the Service’s permissions; they cannot expand its published access.

Try it · Select Admin tasks and open Create task.

Choose Agent task. Script execution appears in the form, but it still needs an isolation adapter; do not treat it as ready-to-run automation.

Try it · Open Task type and select Agent task.

Check the time-zone offset in General settings first. This five-field cron runs every Monday at nine. The task keeps the offset captured when created.

Try it · Verify UTC+08:00, return to the form, select Cron, and enter the expression.

Choose the engine, then an authorized connection and model. Admin CLI tasks can use web access when granted, but cannot use a native terminal.

Try it · Choose the demo Cursor connection and model; leave web access off for this task.

Prepare feedback as a document, then enter the instruction and reference path. Scheduled tasks cannot read Inbox directly; tell them to report missing input.

Try it · Enter a specific instruction and the path relative to docs.

Grant read access to the input folder and write access to the output folder. New blank fields use defaults; clearing existing grants removes access.

Try it · Set the read and write directories, clear Enable immediately, and save.

Select Run now in the task details, then inspect the run record and output file. Saving a task is not proof that it executed correctly.

Try it · Show one sample run, refresh its record, and open the output file.

Once the result is correct, edit and enable the task. If connection permissions change, reselect and save. Task lineage is not a general dependency workflow.

Try it · Edit the task, enable it, save, and inspect its next run.