scheduled ai tasks: what runs, where and when

what the schedulers currently offer

as of 12 november 2026. the limits below describe different things: active schedules, runs per hour and timing options. a blank limit is not an unlimited allowance.

choose the trigger before the tool

a clock is right for work that has a useful deadline: a reading digest before breakfast or a review every friday. an event is right when there is nothing to do until something arrives. avoid a frequent timer that repeatedly asks whether the same document has changed when a less frequent review would do.

as of 12 november 2026, chatgpt documents event-triggered tasks for plus, pro, business, enterprise and edu, but not free or go. claude code cloud tasks also document github events and api calls. these are vendor-specific features; a schedule in one app does not establish that another has the same trigger.²³

read the claude task guide for the difference between cowork and code, or the chatgpt limits guide when choosing a plan.

ten small routine ideas

these are instructions to adapt, not measured results or promises about a vendor's connected apps. give the chosen bot the relevant document or reading material first.

1. daily priority: 'at 8 on weekdays, read my attached plan and suggest the one decision to make first.'
2. meeting rehearsal: 'every tuesday at 9, turn my briefing notes into three questions to practise.'
3. friday reflection: 'friday at 4, ask what went well and what i want to change next week.'
4. study check: 'each evening, quiz me on five terms from the notes i shared.'
5. writing nudge: 'on monday morning, give me one writing prompt based on my draft.'
6. project vocabulary: 'each wednesday, explain one unfamiliar term from our project document.'
7. weekly contradiction check: 'on thursday, flag statements in the attached proposal that disagree with each other.'
8. travel preparation: 'each saturday until my trip, ask which checklist items still need a decision.'
9. reading review: 'every sunday, compare the two articles i gave you and list where they disagree.'
10. monthly reset: 'on the first of each month, help me review my goals before suggesting new ones.'

keep the first version read-only. a reminder to think is useful even when you do not want the bot making changes.

make a dusk routine by saying what should repeat

tell a bot the job, the schedule and where to put the result. it replies with a card showing the schedule and next runs. use Edit, Pause or Undo if the card does not match your intention. Automations in the sidebar lists routines with a calendar and run history.⁸

add a quiet condition such as 'if the document is unchanged, say nothing.' check the first few runs. if the timing looks wrong, ask the bot which time zone it is using. a correct schedule attached to the wrong time zone still produces a bad morning.⁸⁹

for connected apps, reading and drafting can happen freely. sends ask first unless you give the bot a daily allowance. one exception: a bot on Full access with no sending rule of its own may send up to 25 a day without asking, so give full-access bots Ask every time under sending. other app changes need their own boundary: keep access read-only or write 'ask me before you change anything' in the routine.¹⁰

check where the saved job actually runs

as of 12 november 2026, claude's current cowork tasks run remotely, while older tasks created before 6 october that ran locally remain local. claude code also has desktop local tasks that need an awake computer. grok bot documents cloud routines. do not infer an offline guarantee for every product just because it has a schedule.¹¹¹⁶

in dusk, laptop sleep and a closed app stop local routines. a run missed by less than 12 hours runs once when you return; an older one is skipped. choose an always-on home if that delay matters.⁸

gemini schedules have their own delivery window. grok tasks use different names for automations and bot routines. check your provider's current terms and scheduler docs before moving unattended work between tools.