TL;DR
Anthropic’s Claude Code team has published a framework describing four agentic loop patterns: turn-based, goal-based, time-based and proactive. The Thorsten Meyer AI dispatch frames those patterns as a “delegation ladder,” showing what developers and teams can stop doing at each level.
Anthropic’s Claude Code team has published a plain-language framework for agentic AI loops, defining them as repeated cycles of work until a stop condition is met, while Thorsten Meyer AI has framed the model as a four-rung “delegation ladder” for deciding how much work to hand off to AI systems.
The confirmed framework describes four loop types: turn-based, goal-based, time-based and proactive. According to the source material, each loop shifts one more responsibility away from the human operator: checking work, deciding when work is done, starting the work, and eventually forming the prompt itself.
In the turn-based model, the user still starts each cycle with a prompt, but the agent can be given a Skill that checks its own output against defined steps. In a goal-based loop, a separate evaluator model judges whether a stated target has been met or whether the run should stop after a set number of attempts.
The time-based model moves the trigger to a clock, using commands such as /loop locally or /schedule in the cloud, according to the source. The proactive model goes further by using events or schedules to start workflows without a human prompt in real time, often coordinating multiple agents around task-specific goals.
The delegation ladder: four agentic loops, and what each lets you stop doing
Strip the hype and a “loop” is simple — an agent repeating work until a stop condition is met. The useful lens isn’t the mechanics, it’s what you hand off. Four loop types = four rungs of delegation, from a tool you operate to a process that runs.
The whole framework reduces to one question about your own work: where am I the bottleneck, and which single piece can I hand off? Can you write the check? Is the goal concrete? Does the work arrive on a schedule? That answer picks your rung — and you climb one step at a time. The real skill isn’t operating a loop; it’s the judgment of what to delegate and how far — enough hands off to gain leverage, enough on the wheel that “runs without you” doesn’t become “runs away from you.”
Delegation Moves Beyond Prompting
The development matters because it gives teams a sharper way to discuss AI autonomy without treating every agent workflow as the same thing. The model separates using an AI tool from allowing an AI process to run with defined checks, triggers and stopping rules.
For developers, the framework points to practical controls: quantitative checks, clear success criteria, turn limits, lower-cost models where possible and review by a fresh-context agent. For businesses, the larger question is where human review is still needed and where repeated work can be delegated without losing oversight.
AI workflow automation tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Claude Code Sets The Terms
The source credits Delba de Oliveira and Michael Segner of Anthropic with the June 30 Claude blog post, “Getting started with loops.” The definitions, commands and examples are attributed to Anthropic, while the “delegation ladder” framing is attributed to the Thorsten Meyer AI dispatch published July 1, 2026.
The dispatch also repeats Anthropic’s caution that not every task needs a loop. Its recommended approach is to start with the simplest workable setup and move upward only when the task justifies more autonomy, cost and monitoring.
“Each one is defined by what you hand off.”
— Thorsten Meyer AI Dispatch
AI task management software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Limits Still Need Testing
Several details remain unsettled. The source says some features are research previews, meaning availability and behavior may vary across users, environments or future Claude Code releases. It is also not yet clear how widely teams will adopt the four-rung framing outside developer workflows.
Cost and reliability are also open questions. The dispatch warns that autonomy is metered, and that large runs should be piloted before being scaled to many agents. Claims about productivity gains depend on task quality, evaluation design and how well teams define clear stop criteria.
AI process scheduling software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Teams Choose Their Rung
The next step for readers is practical selection: identify where the human is the bottleneck and choose the lowest loop that removes that bottleneck. A team may start by encoding checks in a Skill, then move to goal-based loops when success can be measured with tests, scores or other firm criteria.
For broader automation, teams can test scheduled loops or event-driven workflows, but the source recommends keeping cost controls, review steps and cancellation paths in place. The near-term focus is likely to be less on bigger prompts and more on better systems around the agent.
AI agent development kits
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What is the actual news in this story?
Anthropic published a framework for agentic loops in Claude Code, and Thorsten Meyer AI framed it as a delegation ladder for deciding what work to hand off.
What are the four loop types?
The four types are turn-based, goal-based, time-based and proactive. Each one gives the AI system more responsibility for checking, stopping, starting or initiating work.
What is confirmed versus interpretation?
The loop definitions and Claude Code primitives are attributed to Anthropic. The delegation ladder reading is the author’s framing in the Thorsten Meyer AI dispatch.
Does every AI task need a loop?
No. The source material says teams should start with the simplest workable setup and use more autonomous loops only when the task justifies the added cost and oversight needs.
Why does this matter for businesses?
It gives businesses a practical way to decide how much AI autonomy to permit, from self-checking tasks to scheduled or event-driven workflows that can run with less human involvement.
Source: Thorsten Meyer AI
