AI Loop Engineering & Gauntlet Loops (2026) - The Prompt Index
🎁 Your first month of Pro is FREE — use code FREE at checkout →
Submit Content
Please sign up or log in to submit a Prompt, Image, GPT, AI Tool, or use the AI Toolbox.
Close
Sign Up<br>Log In
1st MONTH OF PRO FREE<br>Enter code FREE at Stripe checkout
Claim Offer<br>×
The Short Answer
AI loop engineering is the practice of designing a system in which an AI acts, observes the result, evaluates it against a defined standard, improves the work, and repeats until a success condition, safety boundary, budget, or escalation rule stops it. You define the objective, metric, and boundary; the loop replaces your manual chain of follow-up prompts.
On this page
What is an AI loop?
Objective, metric, boundary
Prompting vs looping
What is a Gauntlet Loop?
The Claude of Duty prompt
Why the prompt works
Two approaches, kept separate
How to run a Gauntlet Loop
Copy-paste templates
Examples beyond coding
Failure modes and safeguards
FAQ
What Is an AI Loop?
An AI loop is a repeating feedback cycle. The agent does not merely produce an answer and wait for you. It takes an action, examines what actually happened, compares the result with a target, changes its approach, and tries again.
Objective
Build
Inspect
Judge
Improve
Repeat or stop
For code, that may mean edit, run tests, read the failure, revise, and rerun. For a website, it may mean render, inspect screenshots at several screen sizes, compare them with reference sites, fix the largest visual gap, and render again. For a book, it could mean draft a chapter, check it against the outline and style examples, ask a fresh editor to find the weakest passage, revise, and continue.
The action-feedback pattern is not brand new. Research systems such as ReAct formalised cycles of reasoning and action years ago. What changed in 2026 is that mainstream agent tools made long-running goals, subagents, scheduled work, durable skills, and tool use much easier to combine. That pushed the conversation from writing a better individual prompt to designing the system that keeps prompting, checking, and continuing.
The Three Core Elements: Objective, Metric, Boundary
Use objective, metric, and boundary as the smallest useful design card for a loop. It is simple enough to remember and strict enough to expose vague thinking before an expensive run begins.
Element<br>Question it answers<br>Weak version<br>Useful version
Objective<br>What must become true?<br>“Make the site better.”<br>“Rebuild the pricing page so a first-time visitor can compare all plans and complete checkout on mobile.”
Metric<br>What evidence proves an attempt improved or passed?<br>“It looks professional.”<br>“No accessibility violations, no horizontal overflow at 360px, all checkout tests pass, and a fresh critic prefers our hierarchy to the approved reference.”
Boundary<br>What may it change, and when must it stop?<br>“Keep going until perfect.”<br>“Do not deploy or alter billing. Stop after four hours, £25 of model usage, three failed approaches, or any blocker requiring credentials.”
These three elements are the minimum, not the complete machinery. Serious loops also need tools, observable feedback, durable state, error recovery, permissions, and an escalation path. Without those, the loop may repeat, but it cannot reliably learn from the last attempt.
Prompt Engineering vs Loop Engineering
Prompt engineering asks, “What should I tell the model right now?” Loop engineering asks, “What system should decide what the model does next, how the result is checked, what it remembers, and when control returns to me?”
Prompt engineering<br>Loop engineering
Unit of work<br>One request and response.<br>A continuing process with multiple attempts.
Who supplies the next step?<br>Usually the human.<br>The loop chooses the next action from evidence.
Feedback<br>Often your written follow-up.<br>Tests, screenshots, benchmarks, tool results, critics, or approval gates.
Memory<br>The current conversation.<br>Conversation plus files, logs, issue trackers, plans, or other durable state.
Stopping<br>You stop prompting.<br>A success, failure, budget, safety, or escalation condition fires.
This is not the death of prompting. Every stage of a loop still needs clear instructions. The loop supplies the architecture; prompts tell the planner, builder, critic, and verifier how to perform their part.
What Is the Gauntlet Loop?
Matt Shumer calls his specialised builder-versus-critic pattern the Gauntlet Loop . He popularised it through the Claude of Duty experiment: one short orchestration prompt started a many-hour run that produced a technically ambitious browser-based first-person shooter in Three.js.
The pattern is simple:
Give a lead agent an ambitious goal and a concrete example of what great looks like.
Let it split the artifact into the smallest parts that can be improved and judged...