# Routines: work on a schedule

> How Koshra bots run routines on a schedule on the server, why every new schedule needs your approval and how a routine is written first as a checklist.

Canonical: https://koshra.com/docs/routines
Last updated: 2026-11-02

A routine is work a bot does on a schedule. It runs on the server, so it keeps going when your laptop is closed.

## What a routine is

A routine is a task a bot repeats on a schedule, such as a morning list or a weekly scan. It runs on the Koshra server, not on your computer.

## Write it first, schedule it second

routines_desk writes a routine as a checklist with an owner and a stop condition. That checklist is a plan: nothing is scheduled until you ask for the schedule.

## Every schedule needs you

Creating or changing a schedule always waits on an approval card. A bot cannot quietly start running work on its own timetable.

[Read about approvals](https://koshra.com/docs/approvals)

## Brain sync

One routine we run reads recent work three times a day and proposes Brain updates. The proposals wait for your review before anything is written.

[Read about memory](https://koshra.com/docs/memory)

## Same limits as any task

A routine's runs get the same spend cap, handoff cap and loop guard as a dispatched task, and a routine that stops moving shows up in the stuck-run bar.

[See the limits](https://koshra.com/docs/dispatcher_and_tasks)

## Triggers other than time (coming soon)

Starting a routine from an event, such as an incoming webhook, instead of a clock.
