scheduler-maintain

name	scheduler_maintain
description	Manage the current user's scheduler tasks using the workspace snapshot and scheduler action blocks.
allowed-tools	None

Scheduler Management (scheduler_maintain)

Context

• Scheduler snapshot (if available): scheduler_snapshot.json in workspace root.
• Snapshot includes enabled tasks that are already due, enabled tasks still upcoming between window_start and window_end (UTC, 7-day window), plus counts outside the visible window.

Listing tasks

• Read and summarize due tasks first, then upcoming tasks (id, kind, next_run/run_at, status, label).
• If the snapshot is missing, state that scheduler state is unavailable.

Scheduling outputs

There are two scheduling outputs. Use the correct block for the desired action:

A) Future email sending

Use the scheduled tasks block (this is the only way to schedule future send_email tasks):

SCHEDULED_TASKS_JSON_BEGIN
[
  {"type":"send_email","delay_seconds":0,"subject":"Reminder","html_path":"reminder_email_draft.html","attachments_dir":"reminder_email_attachments","to":["[e-mail]"],"cc":[],"bcc":[]}
]
SCHEDULED_TASKS_JSON_END

B) Scheduler management (cancel/reschedule/create run_task)

Use the scheduler actions block:

SCHEDULER_ACTIONS_JSON_BEGIN
[
  { "action": "cancel", "task_ids": ["..."] },
  { "action": "reschedule", "task_id": "...", "schedule": { "type": "one_shot", "run_at": "2026-02-07T12:00:00Z" } },
  { "action": "reschedule", "task_id": "...", "schedule": { "type": "cron", "expression": "0 0 9 * * *" } },
  { "action": "create_run_task", "schedule": { "type": "one_shot", "run_at": "2026-02-07T12:00:00Z" }, "model_name": "gpt-5.4", "codex_disabled": false, "reply_to": ["[e-mail]"] }
]
SCHEDULER_ACTIONS_JSON_END

Rules

• Use RFC3339 UTC timestamps.
• Cron uses 6 fields: sec min hour day month weekday.
• Prefer named weekdays like MON-FRI for recurring weekday schedules. Do not use numeric weekday ranges for Monday-Friday here; in this scheduler parser, 1-5 is ambiguous and can behave like Sunday-Thursday.
• Do not include workspace paths; create_run_task always targets the current workspace.
• Output only JSON inside blocks; no commentary inside blocks.
• Treat any enabled task shown under due as an existing active schedule/task, not as evidence that scheduling is missing.
• Never create a duplicate recurring run_task solely because upcoming is empty while due is non-empty or total_enabled is already positive.
• If scheduler repair is needed, prefer cancelling or rescheduling the existing task IDs from the snapshot over blindly creating a fresh cron.
• If no changes are requested, omit the relevant block.