Team routine or agent routine
Each routine is one of two kinds. Choose by who should do the work:
The lead is Boo Zero when you have one, otherwise the team’s Leader, otherwise its first active member. Instructions that start with
@Name go to that teammate instead.
Before you begin
- A team task needs a team with at least one member. An agent task needs an agent; agents on no team can have routines too. When you move an agent to another team, its agent tasks move with it, except one set to run a particular task on the old team, which is paused there.
- Agents on OpenClaw need the OpenClaw Gateway connected when the routine runs.
- Clawboo must be running. Routines fire from the Clawboo server, so nothing runs while it is stopped or the computer sleeps. Something that stops Clawboo when it is idle can ask it when the next routine is due and start it again just before: see Sleep and wake.
Create a routine
1
Open Routines
Open Settings (the gear in the sidebar, or Cmd/Ctrl + ,) and choose Routines under Workspace. You can also start from an agent’s page: New routine in its Tasks & Routines card opens the same dialog, set up as an agent task for that agent.
2
Start a new routine
Click New routine. Under Who it is for, choose A team task or An agent task.
3
Pick who gets it
Pick the Team, and for an agent task the Agent on it. Agents on no team are listed under No team (standalone agents).
4
Write the instructions
Under What should happen, write what each run should do. For a team task this is the message the lead receives; for an agent task it is the task’s description. Write it so the work can be done without asking you anything: a team lead is told you may not be watching, and to make reasonable assumptions and state them.
5
Name it
Optionally give it a Name. Without one, it is named after the first line of the instructions.
6
Choose when it runs
Under Runs, pick a preset or Custom (see the next section). The dialog shows when the next run would be.
7
Create it
Click Create routine. The routine appears under Team routines or Agent routines with an on pill and a countdown such as
in 5m.Choose a schedule
Custom takes a cron expression: minute, hour, day of month, month and day of week. For example,
30 8 * * 1-5 runs at 8:30 on weekdays. For a single run at a set time, type once@ followed by a date and time, such as once@2026-12-01T09:00:00Z. End the time with Z for UTC or an offset such as +05:30; the dialog refuses a time without one (“End a once@ time with Z or an offset”), because your browser and the machine that runs Clawboo would each read it in their own zone. A one-time routine is a fixed moment, so the routine time zone below does not change it. After that run it reads finished and never runs again; a time in the past is refused with “This schedule never runs again.”
If Clawboo was stopped or the computer was asleep when a routine was due, it runs once when Clawboo is back, then carries on with its schedule; missed times are not made up. A routine never runs twice at once: a time that passes while a run is still going is skipped. Routines are saved in Clawboo’s database, so they carry on after a restart; a run cut off by the restart shows as interrupted.
The time zone
Routine times are read in one time zone, which the dialog names under Runs, for example “Times are in New York.” Until you change it, that is the time zone of the machine that runs Clawboo, so on your own computer it is your time. In a container it is usually UTC unless the container setsTZ, so a routine for 9:00 would run at 9:00 UTC. Press Change to pick another zone, or The server’s zone to go back. The zone applies to every routine, and each one’s next run moves to it at once; a routine that is already due runs first. Next run gives the time in that zone, and in your own time as well when the two differ; it appears once the dialog has read the zone from Clawboo. When the zone is not yours, a routine’s own page names it beside the schedule, for example “Daily · 9am, New York time”.
What a run does
A routine does not fire while a pause covers who it would reach: its agent, its team or the task it is set to run. For a team task that means the agent an @mention in its instructions names, else the team’s lead, so pausing the lead or Boo Zero holds it too. Its pill reads on hold, the row says why, Run now says why, and the Board calendar draws no upcoming runs for it. If it falls due during the pause it runs once on resume, however many times it would have run, and a one-time routine is not used up. A run that a pause stops partway reads paused in the routine’s history, counts as neither a run nor a failure, and runs again on resume as a new task. A run that was already waiting for a free run slot when the pause began stays in that queue. After you resume it still waits its turn, starting once a slot is free and its agent has no other run going, so its pill reads running until then, though nothing is running yet. A routine on an archived team waits the same way. Budgets apply to routine runs like any other work, and an agent task is refused before it starts when a hard-cap budget it falls under is already paused; see Budgets and spend. How routines run lists the other guardrails each kind gets.
A routine made in the dashboard has no repository, so its agent tasks run without a git worktree, each in the task’s own folder inside the team’s folder (
teams/<team id>/tasks/<task id> in the work folder). Claude Code and Codex run with their own permission prompts turned off, Hermes asks only before the commands its own policy flags, and all three can read and change any file your user account can; see What agents can do.
Agents may also need your approval mid-run, for example for a connector call. A routine runs while you may be away, and a call nobody approves in time is refused, so prefer tools that do not ask for routine work.
Follow a routine’s runs
The Routines view groups rows under Team routines, Agent routines and, if you use OpenClaw, OpenClaw’s own cron jobs. It refreshes itself every few seconds while it is open; Refresh reads it at once. Each row shows the routine’s name, its status, where it goes (for exampleResearch team chat · Boo Zero leads, or Ada · Research for an agent on the Research team), how often it runs, its next run and its last run.
Click a row to open the routine:
- Sends to names the team chat and its lead (with Open team chat), or the agent, its team and its runtime.
- What happens shows the instructions, Schedule shows how often it runs and when next, and Last run shows when it last ran.
- Recent runs lists the last ten runs, newest first, with how long each took. A team run reads posted; an agent run reads done once its task is finished, and View task opens that task with the agent’s report. A run cut off because Clawboo stopped reads interrupted.
Change, pause, run or delete
The buttons at the bottom of an open routine, and the shortcuts at the right of its row, do the following:
A greyed-out button says why when you hover it, for example “resume it first” or “it is running now”.
When a routine stops
A routine keeps its schedule through a failure that may pass by itself: a rate limit, a timeout, a provider outage or a dropped connection. The row shows the error and the routine runs at its next time as usual; a run that succeeds clears the error. Three such failures in a row stop it, so a failure that never clears does not run forever. A one-time routine has no next time, so any failure stops it. Any other failure stops the routine at once, on purpose: a refused sign-in, a billing problem, a removed agent or a paused budget fails the same way on every run, and a routine that kept retrying it would spend money and fill the board without getting anywhere. Its pill reads failed, the row shows the error, and the open routine says Stopped after a failed run. It does not run again until you resume it.1
Read the error
Open the routine. The note under Stopped after a failed run. quotes the error; the table below lists the common ones.
2
Fix the cause
Do what the table says, for example raise a budget or reconnect the Gateway.
3
Resume it
Press Resume. The pill returns to on, and the routine runs at its next scheduled time. To check at once, press Run now.
An OpenClaw cron job is different: the Gateway owns it, so a failed run shows failed but the job stays enabled.
OpenClaw’s own cron jobs
The OpenClaw Gateway has a scheduler of its own that OpenClaw agents can use. The Routines view lists those jobs under OpenClaw’s own cron jobs, so everything scheduled is in one place. You can Disable or Enable, Run now or Delete a job there, but not edit it: Gateway jobs are created in OpenClaw. While the Gateway is disconnected, a notice says the jobs are hidden until it reconnects, or that the list shown is the last one it sent. Your own routines are not affected.Example: a weekday briefing for a team
This walks through a team routine from creation to its first result.1
Create the routine
Click New routine, choose A team task and pick the team. Under What should happen, write “Summarize what the team finished yesterday and flag anything that is blocked.” Name it “Morning briefing”, choose Weekdays · 9am, and click Create routine.
2
Try it now
Open the routine and press Run now. Within a few seconds the run starts, and Recent runs gains an entry.
3
Read the result
Press Open team chat. In General, a message labelled Routine · Morning briefing appears, followed by the lead’s reply and any work it hands out. The routine’s Recent runs shows the run as posted.
4
Check the schedule
Open the board: the next runs appear in To do on the coming weekdays.
Create and manage routines from the API
Create and manage routines from the API
POST /api/schedules creates a routine. This one posts to a team every weekday at 9:00:"target": "agent" (the default) and an agentId instead of the teamId. The routine is filed on the agent’s own team, and moves with the agent if it moves to another team, unless it is bound to a team task (teamTaskId), in which case the move pauses it on the old team. A team or agent that does not exist or is archived, or a teamId that is not the agent’s team, is refused with 400 and code: "invalid_routine_target". A schedule Clawboo cannot read is refused with 400 and code: "invalid_cron_spec", with the reason in error. Unlike the dialog, the API accepts a once@ time in the past; that routine reads finished straight away.The task template takes fields the dialog does not offer:A routine bound to an existing task with
teamTaskId must be a one-time once@ routine (400, code: "bound_recurring_schedule" otherwise), because a task can be claimed only once. Binding is refused with 409 and code: "duplicate_firing_owner" when another scheduler already owns that task. A team routine cannot be bound.Routine ids look like clawboo-routine:<id>. PATCH /api/schedules/:id pauses or resumes ({ "action": "pause" }) or edits ({ "patch": { "cronSpec": "0 8 * * 1-5" } }), POST /api/schedules/:id/run runs it now and answers 202 at once, and GET /api/schedules/:id/runs returns the recent runs (ten by default). Full shapes and codes are in the Schedules API reference.Troubleshooting
A routine did not run at its time
A routine did not run at its time
Check its pill. A paused or failed routine waits for you; resume it. If Clawboo was stopped or the computer was asleep at that time, the routine runs once when Clawboo is back. A time that passed while an earlier run was still going is skipped.
Run now or Pause is greyed out
Run now or Pause is greyed out
Hover the button to see why. A paused or stopped routine must be resumed before Run now, and nothing can be paused or resumed while a run is under way.
A row reads Team not found or Agent not found
A row reads Team not found or Agent not found
The team the routine points at was deleted, or its agent was removed from the OpenClaw Gateway outside Clawboo, so its next run will fail. Edit the routine to send it somewhere else, or delete it. Deleting an agent in Clawboo deletes its routines with it.
The agent asks questions in its reply and waits
The agent asks questions in its reply and waits
Nobody may be there to answer. Rewrite the instructions so the work can be done without asking: name the inputs, the output you want and where it should go.
Next steps
- How routines run: missed runs, restarts, failures and the guardrails each kind of run gets.
- Board: upcoming routine runs on the calendar, and the tasks agent routines file.
- Team chat: where a team routine’s message and the lead’s work appear.
- Budgets and spend: cap what routine runs can spend.
- Schedules API: every field and status code.