Scheduling and Output Tools
Level 4 · The tools it uses
The Claude Code tools that run a prompt on a timer and hand work to the cloud. Then the ones that send you pages, alerts and files.
Course contentsLesson 12 of 16
Level 1 · Starting out
Level 2 · Asking before it acts
Level 3 · Telling it how you work
Level 4 · The tools it uses
Level 5 · Growing past one chat
After this lesson you can
- Run a prompt on a timer with /loop
- Tell a session timer from a cloud task
- Name the ways Claude can hand you a result
10 mincovers 10 glossary entries
Worth reading first: Claude Code Session Tools
How Claude runs on a timer and sends you results
Three cron tools run a prompt on a timer inside a session. CronCreate sets one up with a five-part cron time, CronList shows them, and CronDelete cancels one by its 8-letter id. A session holds up to 50. A repeating one ends itself after 7 days. They only fire while Claude Code is open and idle.
You rarely call them by name. Typing /loop with a time and a prompt sets a timer for you. Typing /loop with a prompt and no time lets Claude choose the gap. At the end of each round, the ScheduleWakeup tool picks the next one, between one minute and one hour away: short while a build runs, longer when nothing is happening.
A session timer stops when you close the terminal. For work that must run with your computer off, the RemoteTrigger tool makes cloud scheduled tasks on claude.ai, once called routines. It is what the /schedule command uses. A cloud task runs from a fresh copy of your repo, and it can run at most once an hour.
Claude can also hand you a result in more ways than a chat reply. The Artifact tool turns an HTML or Markdown file into a private page on claude.ai. You can open it, use it, and share it with a link. It asks before it publishes.
One tool sends you an alert on your desktop. With Remote Control, or in a cloud session, it can also send a push to your phone. Another sends a file you can open, such as a report or a chart. A third hands back a code review as a neat list, with a file and a line for each finding.
One tool drafts a note about a problem with Claude Code and saves it on your computer. Nothing is sent until you choose to send it. Another uploads an ONBOARDING.md file and gives back a link that teammates can open. It is for teams on a business plan.
/loop 5m check if the deploy finished and tell me what happenedWorked example
Lucy stops watching the CI page
Lucy pushes a fix and types /loop check whether CI passed. Claude checks after 2 minutes, sees the build still running, and waits 4 more.
The next round finds a green build. Claude says so, sends her a push on her phone, and stops the loop.
The words for this lesson10
Check yourself
You set a /loop to check every hour, then close your laptop. What happens?
Finished this lesson?
Marking it complete also marks its 10 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.