Each loop needs
you less.

A loop is an agent doing rounds of work on its own until a stop rule is hit. There are four, and they differ only in how much you hand off — from checking every change to not being in the room at all.

Loops — 4 Tool — Claude Code Stop — esc / cancel Source — @claudedevs

The ladder

Four loops, one idea.

A loop = an agent doing rounds of work on its own, until a stop rule is hit. The four differ only in how much you hand off — each rung takes one more thing off your plate.

01Turn-based→ hands off the work

You type the task, it works, you review. Every prompt is already this loop.

Use whenyou want to check each change before it ships.

›add a like button, then run the testsPlain prompt

02Goal-based→ hands off the check

Give it the finish line plus a stop rule. It retries and grades itself until done.

Use when"done" is measurable: a number, a passing test.

›get the page under 2s, stop after 5 triesPlain prompt

03Time-based→ hands off the trigger

Set the schedule once. It remembers to run until you cancel.

Use whenthe same check should repeat on a clock.

›/loop 30m: check the site, fix what's brokenShips with Claude Code

04Proactive→ hands off the prompt

An event wakes it, not you. It runs end to end, then pings you.

Use whenan outside event should start it: a bug, an email, a deploy.

›/schedule when a bug is filed: triage, fix, replyShips with Claude Code

STOP ANY LOOP·press esc to interrupt a run·cancel the schedule to end it for good

The one line to keep

By the fourth rung,
you're gone.