Start from Scheduled tasks in the main navigation; on the phone, use its bottom tab. The desktop opens a task workspace rather than requiring a session-sidebar dialog.
Decide what a run should produce
Select a project and create a task. Give it a recognizable name, a prompt, and its model/Agent configuration. Creation needs an available project. Include enough context that a newly started run can work without your current conversation.
Set the schedule and timezone in the editor, then check the next execution time. Enable the task when you are ready. Use the goal option only when the run should continue toward an outcome beyond a single reply.
Test before relying on the clock
Use Run now and inspect its result. A saved schedule proves that the configuration was stored, not that its prompt, credentials or working directory are correct.
Open History in the task workspace to see runs, duration and recorded failures. A run with a session can be opened there. A failure before session creation has no conversation to open. Scheduled sessions are archived outside the ordinary session list; History is the place to find them.
Pause the arrangement, keep the evidence
Pause a task when you want to stop future executions. Deleting a task does not remove its run history. Execution requires the host to be running; do not treat a closed laptop as an always-on scheduler or assume every missed time will be replayed.