Schedules

Run a prompt on a project on a timer, from every 30 minutes to once a week, while OpenOrc is open.

How schedules work

A schedule sends the same prompt to an agent on a timer. Each run starts a new thread in the schedule's project, with the model, mode and location you saved. Use one for work that repeats, such as a nightly dependency check or a weekly look for flaky tests.

Schedules run on your computer, inside OpenOrc. Nothing runs while OpenOrc is closed.

Create a schedule

Click Schedules on the sidebar's rail.
Choose New schedule, the + button in the header.
Fill in the fields below and choose Create.

Field	What it sets
Project	Where the runs work. You can't change it after saving.
Claude account	For a Claude model, the account the runs use.
Name	The schedule's name. Each run's thread is titled with it.
Prompt	The first message of every run.
Runs	Every 30 minutes, Every hour, Every 6 hours, Every day or Every week. New schedules start at Every day.
Model	The model and effort that run the prompt.
Mode	What the agent may do. New schedules start in Plan, which reads and proposes without changing files. See Modes and permissions.
Works in	A fresh worktree for each run, the default, or The checkout. A project without Git or without a first commit can only use the checkout.

Write the prompt as you would the first message of a thread, and say what a good result looks like. For example: "Look for outdated dependencies with known vulnerabilities and propose one task per upgrade worth doing."

Where results go

Each run creates a thread in the schedule's project, titled with the schedule's name followed by a date and time. The agent's work and its reply are in that thread, in the sidebar with your other threads. If desktop notifications are on, you also get one saying the run started.

In Schedules, each row shows how often the schedule runs, when it last ran and when it runs next. Open thread, the arrow button, opens the thread of the latest run. A line under the row reports the latest run: Thread started when it started, or Run skipped, Run cancelled or Run failed with the reason.

Every run is a new thread, and a run in a fresh worktree also gets its own worktree and branch. Delete the run threads you are done with; see Delete a thread for what stays.

Pause, run now and delete

The buttons on each row:

Button	What it does
Pause schedule	Stops timed runs. The row's badge changes from on to off.
Resume schedule	Turns timed runs back on. The next run comes one interval from now.
Run now	Starts a run at once and opens its thread. The next timed run comes one interval after it.
Delete schedule	Removes the schedule. Threads from earlier runs stay.

To change a schedule, click its name, edit the fields and choose Save. A changed Runs interval starts counting from the moment you save.

When a schedule runs

OpenOrc checks its schedules once a minute, and only while it is running and your computer is awake.
The first run comes one interval after you create the schedule. Use Run now to try a schedule straight away.
If a run came due while OpenOrc was closed or the computer was asleep, it runs once at the next check. Missed runs don't pile up.
On macOS, OpenOrc keeps running after you close its window, until you quit it. On Windows and Linux, closing the last window quits it.

The mode decides what a run does while you are away. In a mode that asks before commands or edits, the run stops at the first request and waits in its thread until you answer.

Next steps

Modes and permissionsDecide how much an agent may do on its own, from planning only to editing and running commands.ThreadsA thread is a conversation with a coding agent about your code. Start one, steer it while it works, and pick it up later.Git and worktreesWork in your checkout or give a thread its own worktree and branch, and see what OpenOrc adds to your repository.

Checked against OpenOrc's source on November 9, 2026.