A Claude Code routine is a saved configuration: a prompt, one or more repositories and a set of connectors, packaged once and run automatically in the cloud. It can start on a schedule, from an HTTP call, or on a GitHub event. Routines are in research preview and available on Pro, Max, Team and Enterprise plans.
The three triggers
Each routine can carry one or more triggers, and one routine can combine them.
- Scheduled: hourly, daily, weekdays or weekly, or once at a set time. Times are entered in your local zone. The minimum interval is one hour, and a run scheduled exactly on the hour can start several minutes late, so the docs suggest something like 9:07.
- API: a per-routine HTTP endpoint with its own bearer token. The token is shown once when generated.
- GitHub: pull request or release events, with filters such as author, labels, base branch and draft status.
Creating one
You can create a routine at claude.ai/code/routines, in the Desktop app, or from the CLI with the /schedule command. All three write to the same account. In the CLI, an example from the docs is a daily pull request review at 9am, or a one off run in a week.
How a run behaves
Routines run as full cloud sessions with no permission mode picker. They run shell commands, use skills committed to the cloned repository and call included connectors without stopping for approval. Claude pushes to branches prefixed with claude/ unless the prompt says otherwise, and GitHub branch protection can restrict where it pushes.
A green status in the run list only means the session started and exited without an infrastructure error. The docs say plainly that it does not mean the task succeeded. Open the transcript.
Limits
Scheduled runs, including one off runs, are capped at 100 per hour per account. Run now, API fires and one off re-runs share 30 per hour per routine. API fires are also capped at 100 per hour per account. The docs say none of these limits has overage. Routines also draw down subscription usage like interactive sessions.
Who owns a routine
Routines belong to an individual claude.ai account and are not shared with teammates. Commits, pull requests and connector actions appear as that person. Team and Enterprise owners can disable routines with a toggle in admin settings.
Where it can go wrong
The most common mistakes are vague prompts and too many connectors. By default every connected connector is included, and the docs advise removing any the routine does not need, because Claude can use every tool from an included connector, including writes. See our safety checklist for routines.
Safeguard offers dependency scanning and fix pull requests that stay off by default, and a free scan at gold.safeguard.sh/scan.
Quick check
What is the shortest schedule a routine allows?
One hour. Expressions that run more often are rejected.
Does a routine ask before each action?
No. Routines run autonomously with no permission mode picker, apart from some artifact actions.
Sources
Last reviewed: 19 October 2026.
