schedule_task — Claude Code prompt: what it does, how to install
The schedule_task prompt for Claude Code and ChatGPT creates and manages scheduled user tasks. It runs when you need deferred actions, reminders, or conditional background checks.
Apache-2.0 ★ 9,488 updated 2026-11-16
.claude/commands/schedule_task.mdWhat schedule_task does
The prompt coordinates scheduled plans and reminders through operation parameters. Listing existing plans inspects active items before modification, while editing, pausing, or deleting relies on specific trigger identifiers. Tasks support one-time runs, fixed intervals, and local calendar times with timezone awareness. Condition checks run through read-only web and sandbox tools before triggering the main goal.
It handles notification modes for routine checks or state transitions. Additional configurations include cooldown periods, idle wait times, and fixed text reminders that deliver messages without running a model. Tool confirmation ensures no task is reported as arranged until the underlying operation succeeds.
Editing operations apply partial updates to existing plans while preserving unchanged fields. Specific parameters clear conditions, intervals, or calendar repetitions when set to empty values or zero.
What it helps with
- create a scheduled task or reminder
- inspect existing plans
- modify task parameters and schedules
- pause or delete a scheduled plan
Example prompts for the agent
- Show my scheduled tasks using schedule_task
- Create a reminder for tomorrow using schedule_task
- Pause the task with schedule_task using its identifier
How to install schedule_task
Manually: put the files in place
.claude/commands/schedule_task.mdHow to use
Paste the text at the start of a chat or into project instructions
Questions about schedule_task
How to install schedule_task in Claude Code?
Place the prompt file at .claude/commands/schedule_task.md inside your project directory.
What does schedule_task do?
It helps Claude create, edit, and manage scheduled background tasks, reminders, and condition-based checks.
How do I update an existing task?
Use the edit operation with the task identifier and pass only the fields you want to change.
Source text
schedule_task.md · Apache-2.0
Create or manage this user's scheduled tasks. Use op=list to inspect existing plans before changing one; use its triggerId for edit, pause, resume, delete, run_now or reschedule. Only plans belonging to this conversation are visible or editable. With op=create (default), schedule a future task only when the user asks you to do something later. For a fixed reminder, set reminder to the exact message and goal to its short description; this delivers without running a model. For work that needs app or web operations, omit reminder. Use at for a one-time or fixed-interval start; use repeatAt (one clock) or repeatTimes (several HH:mm clocks in one plan), with repeatZone and optional weekdays for a daily/weekly local clock time, so daylight-saving changes do not shift the clock time. A condition is checked first with read only web and sandbox tools; by default the task runs only when the condition becomes met. Choose notifyWhen by what the user wants: for a routine check of how things are each time (e.g. tell me each morning if it will rain), set notifyWhen=each_time_met so every met check runs the goal; for watching for a change (back in stock, a price drop), keep the default becomes_met. Each check records a key value; the baseline is the value from the last time the goal was started, or from the first check if it has not started yet, so write comparisons against the baseline (e.g. dropped by more than 50 from the baseline). Set cooldownMinutes when the user limits how often to hear about it or the value may flap around a threshold; a cooldown no longer than the check interval has no effect, so leave it out then. Set whenIdle when the user wants the task to wait for an idle period after that time. Do not claim that a future task is arranged until this tool succeeds. With op=edit, use an existing triggerId and send only the fields the user wants changed: other fields and paused/enabled state are preserved. It edits the same plan, not a replacement plan. Set condition="" to remove the condition, reminder="" to switch from a fixed reminder to a normal task, cooldownMinutes=0 to remove the cooldown, repeatAt="" or repeatTimes=[] to remove calendar repetition, or intervalMinutes=0 to remove interval repetition; provide a future at when making a one-time plan. A nonempty repeatAt/repeatTimes switches to calendar repetition, a positive intervalMinutes switches to interval repetition; do not combine them. weekdays=[] means every day. Set enabled=true only if the user also wants a paused plan resumed. Inspect the returned upcoming times and exactAlarm warning before saying the change is arranged. reschedule replaces calendar repetition with the single clock from at; use edit to keep or set several clocks.
© wangzan101 · Apache-2.0 · wangzan101/Mika