/schedule — cron in the cloud

Routines (research preview) that run on Anthropic’s cloud with your computer off — 1-hour minimum interval, plus GitHub-event and API triggers. Triage, docs sync, nightly audits.

/schedule creates routines — cron for Claude Code, running on Anthropic’s cloud with your computer off. The schedule examples below are the recurring jobs people actually run: morning issue triage, nightly test-and-report runs, weekly dependency audits, docs kept in sync after every merge. Minimum interval is an hour, and routines can also fire on GitHub events or API triggers, which is where they stop being timers and start being automation. Because a routine runs unattended, grades matter more here than anywhere else — check the safety grade before scheduling anything with write access. The schedule-examples guide covers cadence patterns; for a scheduled loop with budgets and stop conditions prewired, generate a harness in the builder.

Ship one post a week, learn what works

Loop/scheduleForward FutureB

Six weeks, one variable changed per post; measure replies, saves, and questions, and end with a winner or an honest null.

prompt
→ Claude Code
Find a repeatable weekly post format for [approved account, audience, and topic] through a six-week experiment. If the account, audience, or topic is missing, ask for it before drafting. Obtain approval before publishing anything externally. Each week, draft one short post about a real problem [person, product, or company] solves. Record substantive replies, saves, and questions after the same measurement window. Treat likes as secondary evidence. Keep the audience, topic area, cadence, and measurement window comparable. Change only one meaningful element each week, such as the opening, format, example, or call to action, based on the strongest signal from the previous post. Stop when one format materially outperforms the alternatives, the six-week experiment ends without a winner, approval is withheld, required metrics are unavailable, or the budget is exhausted. Never fabricate engagement data. Finish with every post, its measurements, the variables tested, the winning format or no-winner result, and the next recommendation.
contentlow risk
claude-codecodex
Forward Future ↗

Inbox-zero weekly sweep

Loop/schedulelooprepoA

A scheduled Friday pass that archives read newsletters, trashes spam, and surfaces what needs a reply — protecting unread human mail.

prompt
→ Claude Code
/schedule every Friday at 5pm, run an inbox-zero pass on my email with the ConnectMyEmail MCP — archive read newsletters, move spam to Trash, and surface anything that needs a reply, never permanently deleting mail and never touching unread human messages. Stop after 300 messages per run, verify the unread count dropped, and ask before archiving anything ambiguous.
emailmedium risk
claude-codecodex
looprepo ↗

Draft weekly release notes

Loop/schedulelooprepoA

Every Friday at 2pm, draft release notes from merged PRs into releases/DRAFT.md and verify all links resolve.

prompt
→ Claude Code
/schedule every Friday at 2pm, draft release notes from the PRs merged since the last draft: group changes into features, fixes, and docs, write one plain-English line per change with the PR link, and save to releases/DRAFT.md. Draft only — a human edits and publishes; never post or send anywhere. Verify every PR link resolves and every merged PR since the last run is covered before saving. Stop after 1 pass per run.
automationlow risk
claude-code

Catch schema drift nightly

Loop/schedulelooprepoA

Every night at 3am, dump the production schema and diff it against migrations, filing issues for any drift found.

prompt
→ Claude Code
/schedule every night at 3am, dump the live database schema (`pg_dump --schema-only`) and diff it against the schema produced by applying all committed migrations to a fresh scratch database. Verify the scratch build reports `migrate status` clean before comparing. Any drift — columns, indexes, or constraints present in prod but missing from migrations, or vice versa — gets an issue filed with the exact diff attached and a proposed corrective migration for human review. Read-only against production; never modify the live schema. Stop after 1 pass per run.
databaselow risk
claude-code

/goal + Routines overnight combo

Loop/scheduleSabrina RamonovA

The two-layer answer to how do I run this overnight: /goal drives in-session work to done, while a scheduled Routine keeps recurring unattended work running on Anthropic's cloud with your laptop closed.

prompt
→ Claude Code
/schedule a Routine (runs on Anthropic cloud, laptop closed) for recurring unattended work, and use `/goal` for in-session iterate-to-done — the two-layer overnight pattern. Guardrails: Stop when the goal is verifiably met, or stop after 15 iterations, whichever comes first. Verify each pass by running the relevant tests or checks — self-reported success does not count. Keep changes minimal and never touch files outside the task’s scope.
automationmedium risk
claude-code
Sabrina Ramonov ↗

→ run /audit-skills every Monday morning

Loop/scheduleGitHubA

Community schedule loop for security, sourced from github. Verified exit condition, evaluator-gated.

prompt
→ Claude Code
/schedule → run /audit-skills every Monday morning Guardrails: Stop when the goal is verifiably met, or stop after 15 iterations, whichever comes first. Verify each pass by running the relevant tests or checks — self-reported success does not count. Keep changes minimal and never touch files outside the task’s scope.
securityhigh risk
claude-code
jennydove ↗