Scheduled agent runs — briefings, reports, and recurring work that fires without you asking.

Routines flip the chat loop around: instead of you asking and the agent answering, a routine is an agent run that fires on a schedule with a goal, a set of tools, and a place to drop its output — a morning briefing at 7:30, a Friday retro, a nightly inbox sweep. A relevance check (the heartbeat) decides whether a run's result is worth surfacing or should just be filed quietly, so routines stay useful instead of becoming a notification firehose.

This page is an outline — the full guide is being written. It will cover:

Creating a routine: schedule, goal, tools, and output target
How the heartbeat decides what surfaces
Reading routine output and run history
Three routines worth setting up on day one

For the thinking behind the design, see Routines and the heartbeat loop on the blog, or the Routines overview.