Key insights

• The /loop skill schedules recurring prompts that run automatically while your Claude Code session stays open, for up to three days
• Loop works with natural language and pairs with other skills like Firecrawl and Slack MCP for automated workflows
• All scheduled tasks are session-scoped. Close the terminal and they stop. For persistent scheduling, use the desktop app or GitHub Actions

---

In Brief

Claude Code now has a built-in /loop skill that lets you schedule recurring tasks directly from your terminal. The video from Developers Digest walks through how to set up loops with natural language, combine them with other skills, and manage scheduled jobs. Boris Cherny, Head of Claude Code at Anthropic, describes Loop as "a powerful new way to schedule recurring tasks for up to 3 days at a time."

---

What you'll learn

• How to schedule your first recurring task with /loop or natural language
• How to combine loops with other Claude Code skills for automated workflows
• The limitations you need to know: session scope, timing offsets, and expiry

---

What is Loop?

Loop is Claude Code's built-in scheduling system. It evolved from a community technique called "Ralph Wiggums," which was a way to make Claude Code repeatedly check its own work (0:00).

The problem it solves: when you ask Claude Code to do something complex, it sometimes finishes too early or loses track of the goal after several compaction cycles (when the AI condenses earlier conversation to save memory) (0:22). Loop fixes this by scheduling prompts that fire automatically at regular intervals.

---

Setting up your first loop

You can schedule a loop in two ways: the /loop slash command, or plain natural language (1:07).

---

Interval rules and limits

A few things to know about timing:

• Minimum interval: 1 minute. Anything shorter gets rounded up (1:27).
• Maximum duration: 3 days. After that, the loop expires automatically (1:47).
• Scheduling offset: Tasks can fire up to 10% off their set interval. A 4-hour loop might fire at 3 hours 36 minutes or 4 hours 24 minutes. This is intentional: it prevents thousands of users from hitting the API at the exact same moment (5:10).

---

Practical examples

The video walks through four examples that show what Loop can do.

Auto-fix PRs

"Loop all my PRs, autofix build issues when comments come in, use a Worktree agent to fix them" (0:52). This keeps your pull requests green without lifting a finger.

Slack digest

"Loop every morning, use the Slack MCP to give me a summary of the top posts I was tagged in" (0:57). This uses Model Context Protocol (MCP), a way for Claude Code to connect to external services.

Daily git recap

"Every day at 8 AM, look at my git history and give me a brief update of everything I worked on the day before. Put it on my desktop" (1:51). Claude Code creates a markdown file summarizing yesterday's commits.

Hacker News email automation

The most complex example chains multiple skills together: Firecrawl scrapes the Hacker News front page, filters for AI and development stories, reads the full articles, then sends an email summary via a Gmail CLI skill (3:38).

---

Managing your loops

Three tools handle everything (5:00):

• CronCreate creates a new scheduled task
• CronList shows all active tasks with their IDs, prompts, and expiry times
• CronDelete cancels a task

You don't need to remember job IDs. Just say "cancel the task that scrapes Hacker News every 4 hours" and Claude Code finds and removes the right one (4:42).

To disable the entire feature, use the --disable-cron flag (5:45).

---

Checklist: Common pitfalls

• Session closed unexpectedly? All loops stop when you close the terminal or shut down your computer. This is by design: loops are session-scoped (2:43).
• Task not firing on time? The 10% offset means your task won't fire at the exact interval you specified. A 4-hour loop scheduled at noon might fire at 12:07 instead (5:10).
• Need tasks to survive restarts? Loop is not a replacement for traditional cron jobs. For durable scheduling, use the Claude Code desktop app or set up GitHub Actions (6:42).
• Session too busy? If Claude Code is actively working on a complex task, scheduled prompts may queue until the current work finishes (6:24).

---

Practical implications

For solo developers

Start with a simple loop like the daily git recap. It takes 30 seconds to set up and gives you a useful summary every morning. Once you're comfortable, try pairing Loop with MCP integrations.

For teams

Loop can monitor shared resources like PR builds or Slack channels. Set up a loop that watches for failing CI builds and auto-fixes them using Worktree agents, so broken builds don't block the team.

For automation enthusiasts

Chain Loop with skills to build simple automations that would normally need their own setup. The Hacker News email example shows how you can go from data source to formatted email without leaving your terminal.

---

Test yourself

1. Transfer: How would you use Loop to monitor a production API endpoint and alert you when response times exceed a threshold?
2. Trade-off: When would you choose Loop over a traditional cron job on your server, and when would the cron job be the better option?
3. Architecture: Design a Loop-based workflow that keeps a project's documentation in sync with its codebase. What skills would you chain together, and what interval would you choose?

---

Glossary

---

Sources and resources