Answer: Schedules are defined at deploy time in `bot/schedules/*` and apply to the whole agent, starting a new task session or handing off through `receive`, while reminders are defined at runtime with `createReminder` or `host.reminders`, are scoped to one conversation, and wake an existing conversation. Status: Confirmed Entry: tool/cursor/agents-and-automation/schedules-vs-reminders Revision: 1 Digest: sha256:1b4ad9b8f8004b35 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:09:00Z Last changed: 2026-11-13T03:09:00Z Last verified: 2026-11-20T12:34:06Z Next check: 2026-11-21T12:34:06Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Schedule defined | At deploy time, in `bot/schedules/*` | [1] | 2026-11-20 Reminder defined | At runtime, with `createReminder` or `host.reminders` | [1] | 2026-11-20 Schedule scope | The whole agent | [1] | 2026-11-20 Reminder scope | One conversation | [1] | 2026-11-20 Schedule session | Starts a new task session, or hands off through `receive` | [1] | 2026-11-20 Reminder session | Wakes an existing conversation | [1] | 2026-11-20 Schedule cadence | 5-field cron, in UTC, to the minute | [1] | 2026-11-20 Reminder cadence | `every`, `cron`, `delay`, or `at` | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/reference/schedules.md". https://cursor.com/docs/agent-sdk/reference/schedules.md Role: primary. Accessed: 2026-11-20T12:34:06Z Quote: "At deploy time, in `bot/schedules/*`" (Supports: Schedule defined) Quote: "At runtime, with `createReminder` or `host.reminders`" (Supports: Reminder defined) Quote: "The whole agent" (Supports: Schedule scope) Quote: "One conversation" (Supports: Reminder scope) Quote: "Starts a new task session, or hands off through `receive`" (Supports: Schedule session) Quote: "Wakes an existing conversation" (Supports: Reminder session) Quote: "5-field cron, in UTC, to the minute" (Supports: Schedule cadence) Quote: "`every`, `cron`, `delay`, or `at`" (Supports: Reminder cadence) Snapshot SHA-256: aef07dbccab4473be292dfdf3081b959655f376b54eb88afc8e6b11ce20918b7 (captured 2026-11-13T03:09:00Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:09:00Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:34:06Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:34:06Z Last attempt: 2026-11-20T12:34:06Z Notes and limitations: Extracted automatically from a single official source (section "Schedules vs reminders"). Related: https://latestn.com/tool/cursor/agents-and-automation/scope-skill-to-files How do I scope a Cursor skill to specific files? https://latestn.com/tool/cursor/agents-and-automation/sdk-streaming How do I stream responses from a Cursor Python SDK agent run? https://latestn.com/tool/cursor/agents-and-automation/select-eval-cases How do I select specific Cursor Eval cases to run? https://latestn.com/tool/cursor/agents-and-automation/run-one-measured-round How do I run one measured round of hillclimbing in Cursor? https://latestn.com/tool/cursor/agents-and-automation/scaffold-run-owners-agent How do I scaffold and run the Cursor agentic-owners pull request review agent? https://latestn.com/tool/cursor/agents-and-automation/schedule-cron-cadence What cron format and timezone do Cursor schedules use, and what cadence options do reminders support? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:09:00Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/agents-and-automation/schedules-vs-reminders/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/agents-and-automation/schedules-vs-reminders POST: https://latestn.com/dispute/tool/cursor/agents-and-automation/schedules-vs-reminders with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/agents-and-automation/schedules-vs-reminders?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What is the difference between schedules and reminders in the Cursor Agent SDK? Revision 1, last verified 2026-11-20T12:34:06Z. https://latestn.com/tool/cursor/agents-and-automation/schedules-vs-reminders (accessed 2026-11-21T10:07:39Z). @misc{LatestN_tool_cursor_agents_and_automation_schedules_vs_reminders_r1, title = {What is the difference between schedules and reminders in the Cursor Agent SDK?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/agents-and-automation/schedules-vs-reminders}}, note = {Revision 1; digest sha256:1b4ad9b8f8004b35; last verified 2026-11-20T12:34:06Z; accessed 2026-11-21T10:07:39Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/agents-and-automation/schedules-vs-reminders