Task schedules

Maintenance on autopilot

A schedule is a standing instruction for your project's agent: it runs every hour, every day, or every week (Mondays), and each run is tracked as a normal task — its own isolated workspace, the same merge-back, the same review pipeline. It's how the routine work that keeps a product healthy happens without anyone remembering to ask.

• "Review the error logs, fix anything new, and summarize what changed."
• "Check every page for broken links and repair them."
• "Tidy up the dependency versions and make sure the test suite still passes."

Creating and managing schedules

Schedules live on the project's Tasks page: write the instruction, pick the cadence, and create it. Pause a schedule when you don't need it and resume it later; delete it when it has served its purpose. Each run appears in the active tasks list like any other task, labeled with the schedule it came from.

Schedules and credits

Each scheduled run is a normal agent run and meters usage credits like one. An hourly schedule is a real recurring cost — start with daily or weekly for most maintenance and tighten the cadence only where it earns its keep.