The recurring layer
/schedule on your machine · RemoteTrigger in the cloud · the cost conversation · failure triage for long runs
Cowork has two recurring surfaces. /schedule runs tasks on your desktop on a cadence — cron-shaped, machine-on required, full filesystem and connector access. RemoteTrigger fires one-shot agent runs in Anthropic's cloud — no laptop required, but the working tree is ephemeral and writes that aren't pushed somewhere persistent are gone the moment the run ends.
Anthropic's docs show you both syntaxes. They don't tell you which rituals are worth the token spend, how to budget for the spikes, or what to do when a 3-hour run dies at minute 45. That's what this module is.
Five workflows below: the five rituals worth scheduling, the cloud-vs-desktop decision, the cost conversation, failure-mode triage, and the watch/unwatch matrix. Each ends with the same idea in ChatGPT scheduled tasks, GitHub Actions, and Copilot Workspace — so you can compare without committing.
// Anthropic's launch keynote — the /schedule demo. Watch on YouTube →