Run Limits, Cost, and Plan Tiers
Routines consume two resources: run credits from your daily cap and tokens billed on top of that cap. Understanding how both work — and how to optimize for each — determines whether your Routines fit your budget or blow it.
Quick Reference
- →Pro: 5 runs/day. Max: 15 runs/day. Team/Enterprise: 25 runs/day
- →One complete Routine execution = one run, regardless of token count
- →Tokens are billed separately on top of the daily run cap
- →Use .claudeignore to limit repository context and reduce token cost
- →Model selection: Haiku for checks, Sonnet for analysis, Opus only for first-answer quality tasks
- →Full execution logs with per-run token counts in Desktop app and web interface
- →Failed runs still consume one run credit from your daily cap
Plan Tiers and Daily Run Caps
Routine execution is rate-limited by a daily run cap that resets at midnight UTC. The cap is per account, not per individual Routine — if you have 5 active Routines on a Pro plan, they collectively share 5 runs per day.
| Plan | Daily Run Cap | Notes |
|---|---|---|
| Pro | 5 runs/day | Enough for 1-2 active Routines with daily schedules |
| Max | 15 runs/day | Handles several daily Routines plus webhook-triggered runs |
| Team | 25 runs/day | Shared cap across team members or per-seat (check plan details) |
| Enterprise | 25 runs/day | Custom limits available via contract |
Your daily run cap applies to your total Routine execution count, not per-Routine. Five Routines each triggered once on a Pro plan = 5 runs = cap hit. If a sixth trigger fires that day, it queues or fails depending on your overflow configuration.
This has immediate implications for Routine design. On Pro (5 runs/day), every run must be worthwhile. On Max (15 runs/day), you have room for several daily scheduled Routines plus webhook-triggered runs from CI/CD events. Teams should audit their Routines every quarter to confirm each one still justifies its run cost.
A GitHub webhook that fires on every PR opened consumes one run per PR. On a busy repository with 10 PRs per day, that's 10 runs — your entire Max daily cap before any other Routines fire. Webhook triggers require careful event filtering to avoid run cap exhaustion.