explainx / blog
Andrew Ng maps three loops for AI-native product building — agentic coding (minutes), developer feedback (hours), and external feedback (days). From The Batch June 30, 2026. How they differ from Boris Cherny''s loop engineering.
Jun 29, 2026
Most teams conflate prompt writing with context design, loop orchestration, and harness code. They are four layers of the same stack. Here is how they nest, what breaks when you skip one, and which layer to fix when agents fail.
Jun 20, 2026
Every developer asking "how do I actually build one of these loops?" gets the same answer: five components, three levels, and one feedback gate that says no. This guide walks you from a blank terminal to a working autonomous agent loop in under an hour — no orchestration framework required.
Jun 19, 2026
If you need agent loops today, start at explainx.ai/loops — around 100 copy-ready workflows with kickoff prompts, guardrails, and new entries every week. Matthew Berman's Forward Future library is a similarly strong option with 26 practitioner-contributed recipes; here is how both compare and what early adopters like Theo (t3.gg) are running in production.
TL;DR — June 30, 2026: Andrew Ng published The Batch letter on X framing three loops for 0-to-1 product building with coding agents — after loop engineering went viral from Boris Cherny (Claude Code) and Peter Steinberger (OpenClaw). The loops run on different clocks: minutes (agent writes/tests code), hours (developer steers product), days+ (users and market). Ng built a typing practice app for his daughter over a weekend as the worked example.
Developer Twitter already had a name for the inner loop: loop engineering — design cycles where an agent acts, verifies, and retries until a check passes. Ng does not redefine that mechanic. He zooms out and asks: what loops surround the coding agent when you are deciding what software to build, not only how to ship a ticket?
His answer is three nested loops, each with a different owner and time horizon.
| Loop | Who drives it | Typical cadence | Job |
|---|---|---|---|
| Agentic coding | AI agent (+ spec/evals) | Every few minutes | Write code, test, iterate until spec met |
| Developer feedback | Human developer | Tens of minutes → hours | Steer features, UI, flows; refine spec |
| External feedback | Users, testers, market | Hours → weeks | Validate vision; inform next spec |
This is the loop Boris Cherny and Peter Steinberger popularized under the loop engineering label.
Inputs: Product specification; optionally evals (a dataset measuring performance against that spec).
Behavior: The agent writes code, tests its work, and keeps iterating until the code is bug-free and meets the specification — without the developer sitting in every turn.
Ng dates the idea of closing the loop to roughly end of 2025, and calls it a game changer for productive long runs without human intervention.
Concrete example from the letter: Over a weekend Ng built a typing practice app for his daughter. The coding agent worked for about an hour on its own — including opening a web browser multiple times to inspect what it had built before reporting back.
Cadence: The engineering loop executes quickly. Ng hears from developers that agents may build and test a new version every few minutes. That matches Claude Code /loop and /goal patterns: verification gates, not better one-shot prompts.
This layer is where harness engineering lives — triggers, retries, token budgets, and eval hooks.
Last year, Ng writes, many developers (himself included) acted as manual QA for coding agents — finding bugs by hand, then asking the agent to fix them. As agents test their own code more reliably, that QA time drops. Developers shift upstack to product decisions:
Cadence: Tens of minutes to hours — how often a developer reviews the product and gives steering feedback.
Typing app examples: Ng changed his mind on visual design, cat costumes unlockable as his daughter progressed (she loves cats), and the grown-up login flow for supervising the child's practice.
Spec work is still human-heavy: A clear vision does not automatically become a good agent spec. After seeing an implementation, developers update or clarify the spec. If the agent repeatedly hits the same problems, Ng recommends building evals — the bridge between product intent and the inner coding loop.
Context advantage vs taste: AI-native teams increasingly use AI to summarize usage data, customer feedback, and competitive analysis. Ng still sees humans with a context advantage — they know users and environment better than the model — and prefers that framing over vague "taste." While the human knows something the AI does not, human-in-the-loop stays necessary to inject that knowledge.
The slowest loop: friends, alpha testers, production with A/B tests, and similar tactics. Ng notes these rarely finish in less than hours; sometimes days or weeks.
Flow: External data → developer vision → detailed product spec → agentic coding loop.
With coding agents accelerating implementation, Ng observes more engineers playing a partial product management role. The difficulty, he says, is shaping product vision and balancing building (vision → spec → code) with getting user feedback to evolve vision — you need both.
Enterprise readers (Salesforce on X) noted the outer loop in regulated environments also includes policy, governance, audit, and accountability — not only consumer A/B tests.
| Topic | Cherny / Steinberger framing | Ng's three-loop framing |
|---|---|---|
| Primary focus | Autonomous verify-and-retry inside the harness | Product building from 0→1 |
| Time scale emphasized | Minutes per iteration | Minutes and hours and weeks |
| Human role | Define checks, budgets, specs | Steer vision + spec; not only QA |
| Evals | Tests, linters, benchmarks | Explicit eval datasets when failures repeat |
| PM function | Implicit (ship faster) | Explicit — engineers as partial PMs |
Ng's letter is complementary, not competing. Use loop engineering for the inner loop; use three loops when explaining why your team still needs product review and user research even if the agent runs unsupervised for an hour.
Wil Chung and others on X connected long-running loops to older cybernetics and control theory — maintaining desired stasis, not just spinning. Ng's nested clocks are one product-facing instance of that idea.
Ng's thread drew 235K+ views within hours. Recurring reactions:
None of that invalidates the framing; it clarifies where the loops break without budget, evals, or user access.
For advanced inner-loop patterns (memory, self-correction), see Fable 5 loop design and the context → prompt → loop stack.
/loop, guardrails, cronSources
Andrew Ng's three-loop framing is from The Batch, published June 30, 2026. Tooling, pricing, and agent capabilities change quickly — verify Claude Code, OpenClaw, and subscription tiers before production workflows.