Start Agent work on a schedule and verify each result in Run history.
Use an automation for repeatable work that should start without a manual prompt, such as periodic checks, code maintenance, tests, or report generation. Qoder starts an Agent task on schedule and collects each result in Run history.
The task should be able to finish without live clarification. It needs clear inputs, an observable completion condition, and resources accessible from its execution environment. Local execution also needs a stable working directory; cloud execution cannot depend on your local environment. If each run requires a new judgment or sensitive confirmation, test it as a regular task first.
Select Automations in the sidebar. Choose an entry point based on how much of the workflow is already defined:
When creating an automation, choose local or cloud execution:
Qoder must be running at the scheduled time and able to reach the required network, accounts, and files. Enable Keep device awake to prevent system sleep while Qoder is running and reduce missed schedules or interrupted Agent sessions.
Do not treat a created automation as proof that a scheduled run succeeded. Return to Automations and open Run history:
Update the instructions when a workspace, dependency, or process changes. Pause or delete obsolete automations to prevent duplicate work, stale context, or changes to retired projects.
Decide whether to automate the task
The task should be able to finish without live clarification. It needs clear inputs, an observable completion condition, and resources accessible from its execution environment. Local execution also needs a stable working directory; cloud execution cannot depend on your local environment. If each run requires a new judgment or sensitive confirmation, test it as a regular task first.
Open Automations
Select Automations in the sidebar. Choose an entry point based on how much of the workflow is already defined:
- Select Create with Qoder when you can describe the outcome but want Qoder to help structure the automation.
- Select New automation when the schedule and task are already clear and you want to fill out the form directly.
Choose where to run
When creating an automation, choose local or cloud execution:
- Local execution runs on your computer and suits tasks that need local working directories, files, or Skills.
- Cloud execution runs entirely in the cloud. Adding Skills or local files and uploading your local environment are not currently supported. Write the goal, inputs, and completion criteria directly in the task instructions. Do not require access to paths or Skills on your computer.
Cloud execution is supported on individual plans (Free, Pro, Pro+, and Ultra) and business plans (Teams and Enterprise).
Create an automation
1
Set the name and schedule
Enter an Automation name, choose local or cloud execution, then select the Schedule, time, and Time zone. For local execution, enable Set expiration date when the automation should stop after a defined period; after that date, it pauses and no longer creates executions.
2
Describe the work
In Agent prompt, state the outcome, scope, constraints, and completion check. For local execution, add context or files and select the work folder and model when needed. For cloud execution, enter the task instructions directly; adding Skills or local files is not supported.
3
Choose the task output
Select Independent task when every execution should create a separate task. Select Merged task when results should accumulate in one task and earlier history should be included in the next execution.
4
Review execution authorization
For local execution, review Execution authorization, which enables unattended operation. When it is enabled, a scheduled Agent can call tools without waiting for the confirmations used in a regular task. Limit access to the workspace and operations required for the automation. This switch is not shown for cloud execution.
5
Create the automation
Review the execution location, schedule, and instructions. For local execution, also check the working directory and authorization scope. Then select Create.
Keep local schedules runnable
Qoder must be running at the scheduled time and able to reach the required network, accounts, and files. Enable Keep device awake to prevent system sleep while Qoder is running and reduce missed schedules or interrupted Agent sessions.
Keeping the device awake does not replace reliable power, network access, or account availability.
Verify the execution
Do not treat a created automation as proof that a scheduled run succeeded. Return to Automations and open Run history:
- Use Group by day, Group by week, or Group by month to review different periods.
- Use Filter by automation when the list contains several automations.
- Use Filter by status to focus on failed or pending executions.
- Select Refresh when the latest state is not visible.