Every developer knows the pain: you push code, then you sit there hitting refresh every 15 minutes waiting for a build or test run to finish—and your flow state is gone. In this video, I show you the feature Claude Code quietly shipped that fixes that: Loops. Think of Loops like a cron job, except you’re scheduling prompts (not just bash commands), and it turns Claude Code from a standard chatbot into a background AI agent that does the busy work while you stay heads-down. I walk through what Loops are, how they run inside your Claude Code session/terminal, and the two ways I use them: recurring tasks (like “every minute print hello world”) and one-shot reminders (like “remind me at 3:07pm to push the release branch”). I also break down the internal tools Loops use—Cron Create, Cron List, and Cron Delete—and then get into the fun part: advanced workflows like monitoring a Vercel deployment via CLI and only debugging if it fails, auto-checking PRs and merging when changes are addressed, or running unit tests every two minutes and iterating until they pass. Finally, I’m very real about limitations and cost. Your machine has to stay on, Loops are session-scoped, and recurring loops expire after three days. And because every loop fire hits the Anthropic API like a normal prompt, you need fail-fast prompts (stay quiet on success, act only on failure) so you don’t accidentally drain your API credits.