Claude CodeClaude Code 2.1 · terminal and VS Code · macOS, Linux, Windows
Dashboard
0%
1
Curious builder0 XP earned · 300 to level 2
0 daysFinish a lesson to begin
Badge collection0 of 6 unlocked
32 small wins to finish your pathNext lesson →

Routines and scheduled tasks

A routine is a saved Claude Code configuration of a prompt, repositories and connectors that runs on its own when a schedule or an event triggers it.

Last updated: 28 Sep, 2026 · Claude Code

The last step away from the terminal: work that starts because of a clock or an event rather than because you typed something.

FeatureWhat it isWhere it runs
RoutinesA saved prompt, repositories and connectors, with triggersAnthropic-managed infrastructure
Scheduled tasksA prompt on a schedule from the desktop appYour machine
Remote ControlDriving your local session from a browserYour machine, controlled from elsewhere

A routine is the most automatic of the three. You save a configuration once and attach triggers to it: a schedule like nightly or weekly, an HTTP call to an endpoint of its own, or a GitHub event. It is in research preview, so the details are still moving.

Remote Control is the opposite trade. The work stays on your machine with your files and your environment, and only the interface moves, which is what you want when the job needs your local setup but you are not at the desk.

What is worth automating

The same test as any automation, with one addition. It has to be work whose failure you would notice.

  • Good: a nightly dependency audit that opens an issue. You read the issue or you do not, and nothing breaks either way.
  • Good: a weekly summary of what changed, posted somewhere people look.
  • Careful: anything that writes to a shared branch. Now a mistake at three in the morning is everybody's mistake.
  • No: anything you cannot check afterwards. If you cannot tell whether it went well, it should not run unattended.
The rules are the supervision
Unattended work is limited only by the rules from part 4. Before scheduling anything, read your deny list and your hooks and ask whether you would be comfortable with them being the only thing standing between a bad idea and your repository.
Try it yourself
  • Write down one job you do every week that a routine could do badly, and what would make it safe.
  • Try Remote Control once, then decide whether you trust it more or less than you expected.
PreviousPlugins

Slow is fine. Stopping is the only problem.