Routines and check-ins
Put repeat work on a schedule: a Monday brief, a weekly competitor scan, a morning check of what needs you.
Stop asking for the same thing every week. A routine gives a bot a recurring job. A check-in (heartbeat) has a bot look at something on a schedule and speak up only when there's a reason.
Create a routine
Open Library › Routines and choose Create a routine. Pick the bot, write the brief, set the schedule. Check the timezone and the next run before you switch it on.
"Every Monday at 09:00, check the three competitor pricing pages in this brief. Compare with last week. Link the sources and flag changes. Draft a summary; don't publish."
Make sure the bot has a ready connection and access to its sources. Every run uses model tokens on your provider.
Make check-ins earn their ping
Give a check-in something to look at and a reason to speak: "Every weekday at 08:30, check open support threads and tell me which ones need a decision." That beats "be proactive". Set notifications so routine progress stays quiet and only decisions reach you.
Review, pause, change
Every run lands in the routine's history with its result. If a run fails or needs you, clear that first. Pause a routine before you change its job, remove its bot or swap its connection, then switch it back on.
When routines run
Routines run on your computer while it's on and awake, with Fluf running. Runs missed while the computer was asleep or off don't all replay; check the history and next run after downtime.
Cloud is coming very soon: your bots will run in the cloud with their own computer.