Over the last week you might have seen people having a bit of a lightbulb moment about "loops." It kicked off when Boris Cherny, one of the people behind Claude Code, said something like: "I don't prompt Claude anymore. I have loops running. They prompt Claude and figure out what to do. My job is to write loops." In plain terms: instead of sitting there typing prompt after prompt, you set up a system that prompts the AI for you, over and over, until a job is done. You step outside the loop and design it instead. The frustration I see is that everyone's talking about it and nobody's really explaining how, so it feels a bit like a closely guarded secret. However, we can just ask Claude about it. The building blocks are already in the tools (Claude Code has /loop and scheduled routines built in). You don't need to wait for someone to sell you the secret. Stripped right back, a loop is only four things: - a trigger (a time, an event, or a prompt) - an action (the AI does some work) - a check (something decides whether it's actually good enough) - repeat until it's done, then it tells you That "check" is the bit people skip, and it's the bit that stops the whole thing turning into nonsense on repeat. I've written up a plain-English breakdown with a few marketing examples, I've attached it as a PDF below. In the meantime I'm curious: is anyone here already running loops or scheduled tasks? What for, and what's tripped you up? And if you've not touched it yet, what's the one job you'd love to hand off to a loop?