Claude Code routines for repository work
Claude Code routines execute on Anthropic infrastructure and support schedules, API calls and GitHub events. They remain in research preview. Availability requires a suitable plan and Claude Code web access. Deliberately configure repositories, the environment and connectors for each routine.
Autonomous execution needs bounded effects
A cloud routine is not an interactive run with a person waiting at every step. A good first assignment therefore creates a report or reviewable code change. Publishing, merging and sending messages need separate technical boundaries. The owner also defines budget, missing-data behavior and who receives failure notices.
Verify the actual recurring run
Test the time zone, next scheduled time, output location, duplicate triggering and pause behavior. For local variants, also test a closed session or powered-off device. A schedule is accepted only after a real trigger delivers the correct result. Failures must not present old results as newly generated.
Check the current interface and execution location
Following the 16 September announcement, chat and Cowork are being combined gradually. This does not mean every account already has the new interface. Task dependencies remain decisive: cloud work can continue without a running laptop, while local files, apps or the built-in browser require an available desktop. Test both a normal run and a device interruption. Existing instructions must match the interface actually present in the account being used.
Decision matrix
| Decision point | Proceed when | Stop when |
|---|---|---|
| Assignment boundary | Documented: trigger, input, schedule, sources, review and failure path. | Scope, data or accountability remains unresolved. |
| Workflow evidence | An actually observed scheduled run processes the intended inputs and produces a reviewable result with sources. Missing inputs reach the failure path and external actions remain tied to approval. | There is only an unevaluated demo without acceptance evidence. |
| Operational control | Owner, approval, fallback and next review date are defined. | Avoid: external actions without renewed approval. If the schedule, sources or required approvals remain unresolved, one successful manual assignment does not establish a working recurring routine. |
Keep it verifiable
Primary sources
- Schedule recurring tasks in CoworkSource checked:
- Automate work with Claude Code routinesSource checked:
- Compare Claude Code scheduling optionsSource checked:
- Anthropic: Claude Cowork and chat are now one ClaudeSource checked:
- Anthropic: Claude Cowork and chat are one ClaudeSource checked:
