CoincideFeature
Scheduled tasks
A scheduled task sends a prompt to an agent at the times you choose: a dependency check every weekday at nine, release notes every Friday, a reminder to follow up next Tuesday. It lands in the same thread each time, or starts a fresh thread in a project, and you can ask the agent to set it up for you.
Create a schedule
- In a thread: choose Thread › Schedule…, or the thread’s menu in the sidebar. Each run sends the prompt into that thread as your next message.
- For a project: choose New Thread Each Run… in the Scheduled Tasks panel. Each run starts a new thread in the project with the project’s defaults.
- For a bot: choose Schedule… from the bot’s menu in the sidebar, so it runs in the bot’s conversation. That’s how a bot gets a morning routine.
- By asking: tell the agent in any thread to do something later or on a schedule, for example “Check for outdated dependencies every weekday at 9 and summarize what changed.” It creates the schedule in its own thread.
When it runs
| Repeat | Example |
|---|---|
| Once | Next Tuesday at 10:00 |
| Daily | Every day at 18:00 |
| Weekdays | Monday to Friday at 9:00 |
| On Selected Days | Monday, Wednesday and Friday at 8:30 |
| Weekly | Every Friday at 17:00 |
| Every… | Every 30 minutes, or every 4 hours, from a first run you pick (at least 5 minutes apart) |
| Custom (cron) | A five-field cron expression: minute, hour, day of month, month and day of week |
Every schedule has a time zone, so “9:00” stays 9:00 where you mean it. The editor shows the next few run times before you save.
The Scheduled Tasks panel
Choose View › Show Scheduled Tasks (⌥⌘S), or click the clock at the top right of the toolbar, to see every schedule beside the conversation. It starts with the open thread’s schedules when it has some and shows that thread’s next run. From there you can search and filter schedules, Run Now, Pause and Resume, edit or delete them, and open the thread or its last run.
Each schedule shows how its last run went: running, completed, failed, interrupted or missed, and whether it’s waiting for its thread.
How runs behave
- A run uses the thread’s agent, model and access mode at that moment. If you switch the thread to another agent, later runs go to that agent.
- If the thread is busy, the run waits and is sent when the current turn ends; it never interrupts a turn.
- Schedules run only while Coincide is open. Runs missed while Coincide was closed or the Mac was asleep are skipped, not run late in a burst. To keep a Mac running overnight, see Keep Awake.
- Archiving a thread pauses its schedules until you unarchive it. Deleting the thread pauses them too; delete the schedule, or undo deleting the thread.
Schedules agents create
Every agent Coincide runs can create, change and delete schedules in its own thread through a private connection on your Mac, so this works the same with Claude Code, Codex, Cursor, Grok Build, OpenCode and Antigravity. An agent sees only its own thread’s schedules, never other threads’ or project tasks.
By default, what an agent creates or changes waits behind a card in the thread, and nothing runs until you allow it: review the name, prompt and timing, then choose Save and Allow. No request from an agent, or from a page it reads, can approve it. If you trust your agents with this, turn off “Approve schedules agents create” in Settings › General; you still see and change their schedules in the thread and in the panel.
To keep things tidy, a thread can have at most 10 schedules, with at most 3 waiting for your approval at once, and agents can make only a few changes in a short time.
Limitations
- Schedules don’t start Coincide. If it isn’t running at the scheduled time, that run is skipped.
- A prompt is sent as typed; it can’t include attachments.