@Cander_zhu: In the past two days, @AnatoliKopadze posted two blockbuster contents, and I read both carefully: 1. His ultra-detailed long article "Loops explained: Claude, GPT, Mira and what actually works" (currently over 8...
Summary
This article discusses the application of Loop Engineering in AI agent workflows, focusing on Anatoli Kopadze's detailed explanation of loops and Peter Steinberger's talk at AI Engineer Europe, emphasizing the importance of automated verification loops and acceptance criteria.
View Cached Full Text
Cached at: 06/24/26, 10:30 PM
Over the past couple of days, @AnatoliKopadze dropped two重磅 pieces of content, and I read them both carefully:
- His ultra-detailed longform piece, “Loops explained: Claude, GPT, Mira and what actually works” (now over 8.9 million views)
- Peter Steinberger (creator of OpenClaw) delivering a 19‑minute talk at AI Engineer Europe
Combining @addyosmani’s article “Loop Engineering” with both of Anatoli’s pieces yields a huge amount of insight.
Anatoli’s article lays out the low-level logic of Loops with exceptional clarity:
- A prompt is “you give step-by-step instructions”; a Loop is “you give a goal + acceptance criteria and let the Agent run the result on its own”
- A reliable Loop usually needs these five parts: Automation (trigger), Skill (reusable instructions), Sub-agents (separate the coder from the code reviewer), Connectors (actual execution of actions), Verifier (hard‑core acceptance checking)
And Peter, as the creator of OpenClaw, shares his real-world workflow in the video:
“Each loop is so much faster now that I ship more than ever with way less effort.”
His core takeaways:
- The goal isn’t writing the perfect prompt — it’s designing a closed‑loop that can verify itself
- The Judge (acceptance criteria) determines the Loop’s success or failure; best to use deterministic checks like tests, type checks, diffs, etc.
- Structure your project for the Agent, not against it
I really hope everyone reads these three pieces — ideally together (Addy’s Loop Engineering + Anatoli’s long article + Peter’s video). Theory + practice + framework complement each other, making the overall effect much stronger.
I’ve personally been building a small Loop around “structuring new notes in Obsidian” — still early days, but I can already feel the shift from manual organization to automated workflows.
For anyone interested in Loop Engineering, I strongly recommend reading all three. Theory + real‑world examples + systemic thinking — that combination works best.
Are you leaning toward learning the theory framework first, or would you rather dive straight into practical workflows?
#LoopEngineering
Anatoli Kopadze (@AnatoliKopadze): Peter Steinberger, the guy who built OpenClaw just shared his actual workflow:
“Each loop is so much faster now that I ship more than ever with way less effort.”
19 minutes from the person who knows more about AI agents and loops than anyone else.
Watch it, then read the full
Similar Articles
@Lonely__MH: Prompts Are Dead, Loop Engineering Has Arrived! Recently, the concept of Loop Engineering in AI programming has sparked widespread discussion in the tech community. In a recent interview, Boris Cherny, head of Claude Code, shared what's happening inside the team…
Claude Code head Boris Cherny proposes that AI programming is shifting from prompt engineering to Loop Engineering. In the future, developers' core task will be designing automated loops rather than writing prompts—a trend that could level the development playing field.
@FeitengLi: The loop / loop engineering that's been trending on Twitter recently comes from this May 4 interview — Anthropic's Claude Code creator Boris Cherny (author of a TypeScript book, a coder at heart)...
Anthropic's Claude Code creator Boris Cherny systematically introduced the loop engineering method at Sequoia AI Ascent 2026, stating that programming is now 100% done by AI, and predicted that software will become as democratized as the printing press.
@Phoenixyin13: What does a good Loop actually need? This article finally addresses the most valuable part. The number one priority is a verification mechanism. AI cannot grade itself; it will give itself full marks. There must be an objective way to check, such as code passing tests, the article meeting word count and structure requirements, numbers matching up, etc. Without this, the loop is just a waste…
The article discusses the three most important elements of an AI loop: verification mechanism, memory, and stop condition, and points out the cost-effectiveness issues of current fully automated loops.
@cellinlab: https://x.com/cellinlab/status/2064144608242679822
This article introduces the concept of Loop Engineering — instead of directly writing prompts for AI agents, it designs a system (loop) that recursively lets the agent iterate on tasks until completion. The article provides a detailed comparison of how Claude Code and Codex implement five building blocks: automations, worktrees, skills, sub-agents, etc. It suggests this could be the future trend of collaborating with coding agents, but also warns about token costs and AI slop issues.
@AomyYing: Complete Guide to Loop Engineering: Normal people ask AI one sentence ("Help me write an article"). Experts design a loop that lets AI automatically execute → check → correct → until the result is satisfactory. Core formula (5-step Loop): 1. Define the goal 2. Break down steps 3. …
This tutorial introduces the Loop Engineering method, which designs a cycle of automatic execution, checking, and correction, allowing AI to iterate until the result is satisfactory, upgrading a single query into process engineering.