Define the recurring outcome.
Describe what to check, what information is in scope, and what the agent should produce. Start with a narrow task you can verify easily.
Product / Routines
Use scheduled work for recurring check-ins, reviews, and summaries, with the results kept in your workspace.
A practical starting point
Describe what to check, what information is in scope, and what the agent should produce. Start with a narrow task you can verify easily.
Match the schedule to the work. An overnight check needs an available host and model connection; a more frequent schedule can create unnecessary cost or duplicate work.
Inspect the output and any failures before relying on the routine. Adjust the instructions if the updates are noisy, incomplete, or hard to act on.
Put it into practice
Ask an agent to review the project’s current tasks and notes, identify work waiting for a decision, and prepare a short summary with links or paths. Specify the project and the time period so the scope stays clear.
Have the summary separate completed work, open issues, and questions for you. If a check fails, the routine should explain which step failed instead of presenting an empty summary as success.
Scheduled work is still agent work: it can call models and enabled tools. Review its access, provider usage, and output just as you would for a task started in chat.