'Loop engineering' goes mainstream as agent iteration gets a name
Posts by the creators of Claude Code and OpenClaw gave a discipline a name — and sparked a field-wide conversation about how AI agents should actually be built.
Spotted on X: "loop engineering" — the practice of designing AI agents to iterate reliably on software problems — became this week's most-discussed phrase in AI development after posts by Boris Cherny, creator of Claude Code, and Peter Steinberger, creator of OpenClaw, went viral on social media.
Andrew Ng wrote a letter on the moment. His framing: loops are "a key part of how we get AI agents to iterate at length to build software." The implicit contrast is with one-shot prompting — where the agent gets a single attempt and the developer reviews the output. A loop-first design flips the priority: structure the iteration cycle first, write the prompts that serve it.
Naming matters in engineering disciplines. When a practice graduates from "the thing we do" to "loop engineering," it accelerates — practitioners compare notes, share patterns, and build shared vocabulary for the failure modes. The questions that follow naming are the productive ones: how many iterations to budget per task, how to checkpoint progress inside a long-running agent, and how the loop knows it's finished rather than just stuck.
For teams building on AI agents today, this is less a warning and more a prompt. The tools exist, the name exists, and the discipline is being written right now. Teams that engineer their loops deliberately — rather than hoping the model figures it out — will have a structural advantage that compounds as agents take on more complex work.
