Schedule

Schedule runs a prompt automatically, on a repeating cadence from hourly up to weekly, without you starting the chat yourself. Each run either opens a new chat (built-in agent, with its own model and thinking level) or sends the prompt to a chat you’ve already pinned in the sidebar — including one backed by a CLI agent.

​

Open the Schedule panel

Click the Schedule button in the sidebar, directly below Plugins. It opens a drawer with two tabs:

• Schedules — create, edit, and manage your scheduled tasks.
• Activity — a combined feed of every run across all schedules.

​

Create a schedule

Click New schedule on the Schedules tab.

• Name — a short label, up to 200 characters.
• Prompt — the instruction the agent runs each time, up to 20,000 characters. Runs are unattended, so write a prompt that’s self-contained — the agent can’t ask you a clarifying question mid-run the way it would in a live chat.

​

Cadence

Choose Repeat:

• Hourly — fires every hour, at a minute you choose (0–59).
• Every N h — fires every 2, 3, 4, 6, 8, or 12 hours, at a minute you choose.
• Daily — fires once a day at a time you choose.
• Weekly — fires on one or more days of the week you pick, at a time you choose.

Times are always your computer’s local wall-clock time — there’s no timezone selector. A schedule set for 9:00 AM keeps firing at 9:00 AM local time across daylight-saving transitions, even though the actual interval between runs shifts by an hour on the transition day.

​

Choose a target

Pick Target: New Chat or Pinned Chat.

​

New chat

Each run creates a fresh chat with the built-in agent:

• Project — Main Chat, or one of your open projects.
• Model and thinking level — the same selectors as the chat composer. These are set per schedule and apply to every run.

​

Pin a chat as a target

To target an existing chat instead, right-click it in the sidebar and choose Pin Session first — the Pinned chat dropdown only lists chats you’ve already pinned. Each run sends the prompt to that chat using its own saved model and thinking level, not a per-schedule choice. This works the same way whether the pinned chat runs on the built-in agent or a CLI agent — the CLI engine drives the scheduled prompt exactly as it would a message you typed yourself.

​

Manage a schedule

From the Schedules tab or a schedule’s own detail view:

• Toggle — enable or disable a schedule without deleting it. Re-enabling recalculates its next run time.
• Run now — fires the schedule immediately, without affecting its regular next run time.
• Delete — requires a second click within a few seconds to confirm, and also removes its run history.

Catch up missed run and Notify on completion are per-schedule options in the detail view — see Missed runs and Notifications.

​

Missed runs

If CTOR was closed when a run was due, what happens next depends on the schedule’s Catch up missed run option:

• On (the default for Daily and Weekly) — the schedule fires once, shortly after CTOR next launches, no matter how many occurrences it missed while closed.
• Off (the default for Hourly and Every N h, since those cadences catch up again soon regardless) — the schedule doesn’t fire late. Instead, a skipped entry recording how many occurrences were missed appears in its run history.

​

Overlapping runs

If a run is still in progress when the next one is due, the new run is skipped and recorded rather than queued or run in parallel — for a pinned chat that’s still busy, or for a new-chat schedule whose previous run hasn’t finished yet.

​

Auto-disable

A schedule targeting a pinned chat disables itself automatically if that chat is later deleted or archived, and shows the reason inline on the schedule. Re-enabling it after pointing it at a valid chat again clears the notice.

​

Notifications

When Notify on completion is on (the default), CTOR posts a system notification when a run finishes successfully. A failed run always notifies, regardless of the toggle. Clicking a notification brings CTOR to the foreground; opening the run from the Activity tab jumps straight into the chat it ran in. Scheduled runs don’t also trigger CTOR’s generic turn-end notification — you only see the one for the schedule.

​

Activity and run history

The Activity tab lists every run across all schedules, most recent first; a schedule’s own detail view shows its recent runs the same way. Each entry shows its status (success, error, running, or skipped), when it fired, how long it took, and a link to open the chat it ran in, when that chat still exists. Archiving the chat a run happened in hides that run from these history views — including the success/error counts shown next to each schedule — until you unarchive it. Runs with no associated chat (skips and misses) and runs whose chat was deleted stay visible, since the run entry is the only record that they happened.

​

Sidebar indicators

• The Schedule button shows a small dot when at least one schedule is enabled.
• A chat created by a schedule shows a small clock icon next to its title in the sidebar.

​

Manage schedules from Main Chat

You can also ask the main chat agent to create, list, update, delete, or immediately run a schedule in conversation — for example, “Schedule a daily summary of open PRs at 9 AM in a new Main Chat”. This works whether the main chat itself is running on the built-in agent or a CLI agent, and schedules created this way are identical to ones created through the panel — they show up together and either surface can manage them.

​

Turn scheduling off

Scheduled tasks are on by default. To turn the feature off entirely, disable Scheduled tasks under Settings → Agent — existing schedules are kept but stop firing until you turn it back on.

​

Next steps