Scheduled Code tasks
How to create and monitor local Code schedules, and how they differ from account-backed Chat schedules.
Find scheduled work
Open Scheduled Tasks in the desktop navigation rail to review local Code automations. When account-backed Chat scheduling is available, the same view can show Chat and Code rows together with All, Chat, and Code host labels. A Code schedule is tied to this computer and its selected project or task. It does not become a hosted Code schedule or sync Code state to the account.
Create a Code schedule
Use the create control in Scheduled Tasks. The dialog is titled New scheduled task. Name identifies the routine, and What should the agent do? contains the instruction. Continue in selects New chat, New chat in <project>, or an existing task. Run with selects the Code runtime, model, and optional reasoning. Permission ceiling sets Read only or Project write, with Full access or automatic choices only when the draft and runtime permit them. Delegation can be Off or Auto when supported.
Once and Repeat define whether the routine runs one time or on an interval. Repeat accepts minutes, hours, or days. Run at or First run at sets timing, and Build on previous runs controls whether later runs use the preceding run as context. Create saves the routine on the local computer.
Monitor and change a routine
Select a schedule to open its details. Setup and Runs tabs separate configuration from execution history. Pause and Resume control future runs; Run now starts an immediate run; Save applies edits. A run can report queued, active, completed, or failed status. Open chat returns to the associated Code task so output and evidence can be reviewed in context.
Mobile availability
The phone’s Scheduled Tasks destination requires account-backed Chat for the schedule list. With Chat available, the phone can show Chat schedules and reachable paired-computer routine rows, filter by host, open a Chat or Code task, and expose actions such as pause, cancel, run now, and run history when the host allows them. Code-specific authoring remains a desktop Scheduled Tasks workflow. A phone does not create a cloud Code scheduler, and a Code routine remains bound to the paired computer.
Tasks, Runtimes, Orchestration, and Mobile provide related guidance.