Skip to main content
A routine is work a bot repeats on a schedule: every weekday morning, pull the report; on Fridays, check the release page; every hour during business hours, watch the queue. Routines belong to a bot you own and fire in your local weekday hours.

Set one up

1

Sign in and open a bot you own

Guests cannot create routines; a routine has to belong to an account that can come back and stop it.
2

Add a routine

Describe the repeated work and when it should run. The bot can also create one for you from the conversation — do this every weekday at nine — through its routine tool.
3

Choose how it reports back

Ask for a notify when something changes, or a short message each run.
4

Pause and resume from the Computer rail

Routines are listed on the rail with their state.

Timing

A run wakes the bot’s computer if it is asleep, does the work, and reports through the user-visible tools. Consequential steps inside a routine still park behind approvals unless you chose Always for that kind of step earlier.

Routines follow your account

Your chats, projects, and Bot routines follow a signed-in account across devices — the web app and the Bot desktop app show the same routines.

When a routine runs

A routine is not a turn you started, so it has to be able to run without you watching. Two things follow from that:
  • The computer wakes first. A routine on a bot whose guest is asleep resumes the guest before the model is prompted, the same way a turn does. The bot starts with its shell and desktop available. See Computer.
  • Approvals still apply. A consequential step inside a routine parks behind Allow / Deny / Always unless you already chose Always for that kind of step. A routine does not silently gain permission because you are not there to watch it.
A routine that hits the 15-minute turn deadline ends there; the work it already did stays. Long jobs belong in a background task inside the routine. See How Bot works.

Routines are not…

  • Computer — where routines run.
  • Toolsroutine, notify, send_to_user.