All 15 AI Loops People Run 📚

The single most-demoed loop in the whole pull, from a creator named raycfu whose walkthrough did 43,587 views and 1,040 comments on Instagram. Two agents: a builder that writes code and a checker that runs the tests, types, and lint and reports exactly what broke. They pass work back and forth until it is clean. The whole pitch is the pain it kills: a one-shot agent ships its bugs.

This is the loop in Boris Cherny’s own words, and the highest-engagement description of it (@bcherny, 781 likes): run Claude Code plus an advanced model plus a verifier in a loop, feed it tasks, and remove bottlenecks as you go. The verifier is the part everyone skips. Without it you are just trusting the agent.

The most-watched actually-set-one-up video, from AI Jason (15,436 views, 537 likes), ships a free loop-engineer template: a codebase harness plus a knowledge template you clone, point at your repo, and run, so you are not wiring the build, observe, verify, and stop scaffolding from scratch. The fastest on-ramp if you want a loop running tonight without designing the plumbing yourself.

Peter Steinberger, who merged 859 PRs across his repos in the last 30 days at a 95 percent acceptance rate, runs this one on a tight timer: every five minutes while he is working, the agent does one small, verified piece of upkeep. What to clean is the agent’s call, not a hardcoded script. That decision is the whole point.

A creator named qbuilder (4,560 views, 125 likes on TikTok) runs a bounded version that fixes the runaway problem cold: plan, generate, verify, fix, repeat, with everything saved to files and a hard cap of five iterations. You only read the final version. The cap is what makes it safe to leave.

roborev is a free, open-source code-review tool (a Go binary; install from roborev.io) that surfaced in the research through Dan Kornas. It installs a git hook so every commit triggers a background review, then feeds the findings into an agentic fix loop while the context is still warm. The launch tweet was quiet at 20 likes, but the repo is the real signal: 1,410 stars and commits shipping the same day I write this. It is the installable version of the one thing this whole piece argues is the hard part, a verifier living inside the loop, and it plugs into Claude Code, Codex, and Gemini CLI.

The breakout skill of the month, surfaced by evgenii.arsentev (32 likes, 950 views) and sitting at 600-plus stars in days: a skill whose only job is to turn a vague ask into a rigorous goal, specifying the result, how to verify it, what not to touch, and when to stop. As he put it, your agent is not dumb, your instructions are just vague.

A builder on r/LangChain posted the full architecture for an email agent that processes 15,000 hotel guest emails a day: it loops the inbox, classifies and drafts, and escalates only what needs a human. It is the rare Reddit post that ships the whole production loop, not a demo.

The best-designed loop on Reddit, a Claude Code skill posted to r/claudeskills. It runs an autonomous build, audit, and verify cycle until a machine-checkable contract passes, with explicit anti-spin stops: no-progress detection, a retry cap, flip-flop detection, and a budget. It exists because, as the author puts it, most agent loops never stop to ask whether they are actually making progress, so they retry the same broken approach or quietly edit the test to pass.

The line that started all of this, from the man who built Claude Code: he does not write code anymore, he writes loops, and they write the code while he sleeps. The most-shared version (@0xMovez, 984 likes) puts a number on it: 30 percent of his code is now fully written by loops. The shape is a scheduled routine that watches your PRs and lands the fixable ones overnight.

The most practical pattern from the no-code crowd, from a thread on r/n8n: the workflow runs, then pauses and sends you a message with approve, revise, or skip buttons, treating human review as its own queue with reminders and deadlines. Same loop shape, but the stop condition is your approval instead of a passing test.

Berman’s highest-utility goal. It reads your production logs, separates real actionable errors from noise, fixes the actionable ones with a test, and opens a PR. The value is the triage; tell it what “actionable” means or it chases ghosts.

Berman again, and the one that respects how flaky “it works” really is. It does not stop at the first green run; it tests realistic scenarios and only declares victory after a streak passes in a row. One green run is luck. A streak is reliability.

Lukas Kucinski’s Clodex loop has Codex review Claude’s pull requests before merge, so two different model families have to agree before code lands. Paste it verbatim.

The --max-iter 5 and --threshold medium are the whole point. It argues with itself up to five times and only passes work that clears the bar.

3goblack’s loop (@Dis_Trackted) fixes the most common failure: an agent that says “done” when it is not. Before any work starts it writes a contract of what “complete” means and what evidence proves each requirement, then refuses to claim success without that evidence.