Pre-GA Helix is in Design Partner and Early Access. Early Access opens in the second half of August 2026. Design Partner and Early Access only. Request access
Functions under functions/_scheduled/ can run on a cron schedule instead of an HTTP route. Schedules fire on the deployed platform, not in local dev.
npm install @trayai/helix-cli@0.93.0 @trayai/helix-sdk@0.93.0A file under functions/_scheduled/ that default-exports defineSchedule({ cron, timezone?, handler }) runs on a schedule rather than on an HTTP request. cron is a five-field standard expression and timezone is an IANA name, defaulting to UTC. HTTP was the only trigger until now, so anything periodic had to be driven from outside Helix.
The handler receives the core ctx surface plus ctx.trigger, carrying scheduledAt, firedAt, and isManual. The request-derived fields are absent, because there is no request. ScheduleContext and ScheduleTrigger are both exported.
helix deploy registers schedules instead of refusing the deployProjects containing functions/_scheduled/ were previously blocked at deploy time.
Docs →
helix dev no longer warns about the scheduled directorySchedules fire on the deployed platform, so there is nothing to run locally and nothing to warn about.
Docs →
defineSchedule patternThe AI context layer that helix init writes (CLAUDE.md, the skills, and the Claude Code hooks) now covers schedules, so an assistant working in a fresh project generates the right shape.
Docs →