Vercel Schedules

Vercel Cron Jobs have always been static: you list them in vercel.json, they sync when you deploy, and they run in UTC. Fine for "clean up at 2am". Useless for "remind me Friday at 9".

Vercel Schedules (public beta, November 2026) keeps that static option and adds a dynamic one. Your code can create, change or cancel a schedule at runtime, no redeploy:

import { Schedules } from "@vercel/schedules";
await Schedules.create({  name: `reminder-${id}`,  namespace: userId,  expression: { type: "single", at: "2026-11-07T09:00" },  timezone: "America/Toronto",  target: { topic: "reminders" },  payload: { userId, task: "Follow up with Sam" },});

Three things to notice:

1. One-off or recurring. expression is either single with a local time, or a cron expression.
2. Delivery goes to a Queue topic. A dynamic schedule doesn't call an HTTP path. It publishes to a Vercel Queue topic with your payload, and a handler you write consumes it. Static schedules can still target a function or a path directly.
3. Timezones are real. timezone means "9am Toronto" stays 9am through daylight saving, which a UTC cron never managed.

Why I care: my life agent, Cael, runs two static crons today. With Schedules it can set its own reminders while we talk, which is the difference between a scheduled script and an agent that plans ahead.