Automate work with routines changedroutines
Nearest release: v2.1.285, published 9 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 30 Sep 2026 03:21 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 30 Sep 2026 03:37 UTC.
Upstream edited
Recorded here
Lines+18added
Lines−8removed
From line
58
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits21to this page, all time
The whole hunk
from line 58, old and new numbered
/
from line 58
5858
5959In every other case, including publishing a new artifact, Claude asks first. When a routine's job is to keep a page current, give it an artifact you already published.
6060
61Routines belong to your individual claude.ai account. They are not shared with teammates, and they count against your account's daily run allowance. Anything a routine does through your connected GitHub identity or connectors appears as you: commits and pull requests carry your GitHub user, and Slack messages, Linear tickets, or other connector actions use your linked accounts for those services.
61Routines belong to your individual claude.ai account. They are not shared with teammates, and their runs count against your account's [usage and limits](#usage-and-limits). Anything a routine does through your connected GitHub identity or connectors appears as you: commits and pull requests carry your GitHub user, and Slack messages, Linear tickets, or other connector actions use your linked accounts for those services.
6262
6363### Create from the web
6464
from line 156
156156
157157The same local-to-UTC conversion as recurring schedules applies to one-off timestamps.
158158
159One-off runs do not count against the daily routine run cap. See [Usage and limits](#usage-and-limits) for details.
159One-off runs count against the same hourly limit as other scheduled runs. See [Usage and limits](#usage-and-limits) for details.
160160
161161### Add an API trigger
162162
from line 230
230230A GitHub trigger starts a new session automatically when a matching event occurs on a connected repository. Claude Code doesn't reuse sessions across events, so two PR updates produce two independent sessions.
231231
232232<Note>
233 During the research preview, GitHub webhook events are subject to per-routine and per-account hourly caps. Events beyond the limit are dropped until the window resets. See your current limits at [claude.ai/code/routines](https://claude.ai/code/routines).
233 GitHub webhook events are subject to per-routine and per-account hourly caps. Events beyond the limit are dropped until the window resets.
234234</Note>
235235
236236The Claude GitHub App must be installed on the repository you want to subscribe to, whichever surface you configure the trigger from.
from line 375
375375
376376## Usage and limits
377377
378Routines draw down subscription usage the same way interactive sessions do. In addition to the standard subscription limits, routines have a daily cap on how many runs can start per account. See your current consumption and remaining daily routine runs at [claude.ai/code/routines](https://claude.ai/code/routines) or [claude.ai/settings/usage](https://claude.ai/settings/usage).
378Routines draw down subscription usage the same way interactive sessions do. See your current consumption at [claude.ai/settings/usage](https://claude.ai/settings/usage).
379379
380When a routine hits the daily cap or your subscription usage limit, organizations with usage credits turned on can keep running routines on metered overage. Without usage credits, additional runs are rejected until the window resets. Turn on usage credits at [claude.ai/settings/usage](https://claude.ai/settings/usage). On Team and Enterprise plans, an admin turns them on for the organization at [claude.ai/admin-settings/usage](https://claude.ai/admin-settings/usage).
380Separately from subscription usage, each way of starting a run has an hourly limit:
381381
382One-off runs do not count against the daily routine cap. They draw down your regular subscription usage like any other session.
382| Action | Limit | Counted for | Over the limit |
383| :- | :- | :- | :- |
384| Scheduled runs, including one-off runs | 100 per hour | Your account | The run waits until the limit resets |
385| **Run now**, API fires, and setting a one-off routine to run again | 30 per hour | Each routine, one count shared by all three | The action fails until the limit resets |
386| **Run now** and setting a one-off routine to run again | 100 per hour | Your account | Same |
387| API fires | 100 per hour | Your account, counted separately from **Run now** | Same |
388| GitHub events | See [Add a GitHub trigger](#add-a-github-trigger) | | |
389
390None of these hourly limits has overage.
391
392When a routine hits your subscription usage limit, organizations with usage credits turned on can keep running routines on metered overage. Without usage credits, additional runs are rejected until your usage window resets. Turn on usage credits at [claude.ai/settings/usage](https://claude.ai/settings/usage). On Team and Enterprise plans, an admin turns them on for the organization at [claude.ai/admin-settings/usage](https://claude.ai/admin-settings/usage).
383393
384394While your subscription is paused, your routines are put on hold and don't run. Once your subscription is active again, turn them back on.
385395
No line in this hunk matches that.