TL;DR
Anthropic’s Claude Code team published guidance on agentic loops on June 30, 2026, defining them as repeated work cycles that run until a stop condition is met. Thorsten Meyer AI’s July 1 analysis reframes the four loop types as a “delegation ladder,” showing what developers and teams can hand off at each stage.
Anthropic’s Claude Code team has published new guidance on agentic loops, defining a loop as an agent repeating work cycles until a stop condition is met, while a July 1 analysis from Thorsten Meyer AI frames the guidance as a practical ladder for deciding how much work to delegate to AI systems.
The confirmed development is Anthropic’s publication of “Getting started with loops” by Delba de Oliveira and Michael Segner on the Claude blog on June 30, 2026. According to the source material, the post describes loop patterns used with Claude Code and related tools, including turn-based skills, goal-based loops, time-based loops, and proactive workflows.
Thorsten Meyer AI’s July 1 article interprets those loop types as a four-rung delegation ladder. In that framing, users first hand off verification, then the definition of completion, then the trigger that starts work, and finally the prompt itself in event-driven workflows.
The analysis also carries Anthropic’s warning that not every task needs a loop. The practical recommendation is to begin with the simplest working setup and move to more autonomous patterns only when the task has clear checks, measurable goals, or recurring demand.
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 Becomes the Design Choice
The development matters because it gives developers and managers a clearer way to discuss AI autonomy without treating it as a single yes-or-no decision. The framework breaks autonomy into separate handoffs: checking work, deciding when work is done, starting work automatically, and creating work from events.
For technical teams, that distinction can affect cost control, quality checks, and operational risk. A goal-based loop with a turn cap, for example, can let an agent keep improving a task while limiting runaway model use. A skill with built-in verification can reduce repeat human review for routine changes.
For businesses, the broader point is that agent systems are moving from tools people operate toward processes people supervise. The source material frames the central question as where the human is the bottleneck and which single piece of work can be handed off next.
Agentic AI Engineering: Building AI Agents for Beginners: A Hands-On Guide to No-Code Workflows, LLM Tools, RAG, Automation, and Safe Multi-Agent Systems
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Claude Code Guidance Behind It
The source material says the Anthropic post defines a loop in plain terms: an agent repeats cycles of work until a stop condition is reached. Thorsten Meyer AI’s article argues that the useful lens is not the mechanics alone, but what the user hands off at each stage.
The first rung, turn-based skills, still begins with a user prompt, but the agent can validate its own output through encoded checks. The second, goal-based loops, uses a stated goal and an evaluator model to keep work going until the goal is met or a maximum number of turns is reached.
The third rung, time-based loops, starts work on an interval through local or cloud scheduling. The fourth, proactive workflows, is described as event-driven and able to coordinate many agents without a person issuing each prompt in real time. The source notes that some features are research previews, so availability may vary.
“The useful lens isn’t the mechanics, it’s what you hand off.”
— Thorsten Meyer AI
AI task delegation software
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Preview Features Limit Adoption
Several details remain dependent on tool availability and implementation. The source material says some features are research previews, and it does not establish how broadly each loop type is available across accounts, environments, or Claude Code setups.
It is also not yet clear how teams will measure the long-term impact of these patterns on software quality, model spending, or human oversight. The article presents the delegation ladder as an interpretation of Anthropic’s framework, not as an official Anthropic label.
AI process management tools
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Teams Test One Rung
The next step for teams using Claude Code is likely to be small pilots that add one loop pattern to a well-defined workflow. The source material recommends choosing the rung based on the current bottleneck: whether the team needs the agent to check its work, meet a concrete goal, run on a schedule, or respond to events.
Developers will also need to watch usage costs, set clear stop criteria, and prefer deterministic checks such as tests, scores, or measurable thresholds. Anthropic’s docs at code.claude.com/docs are the stated reference point for implementation details.
AI project automation platforms
As an affiliate, we earn on qualifying purchases.
As an affiliate, we earn on qualifying purchases.
Key Questions
What did Anthropic publish?
Anthropic’s Claude Code team published “Getting started with loops” on June 30, 2026, describing loop patterns for agentic work.
What is the delegation ladder?
It is Thorsten Meyer AI’s framing of Anthropic’s loop types as four levels of handoff: verification, completion criteria, work triggers, and event-driven prompting.
Are all these loop features fully available?
The source material says some features are research previews, so availability may differ by tool, account, or environment.
Why should developers care?
The framework helps teams decide when to use manual prompting, when to add self-checking, and when more autonomous work is worth the cost and oversight.
Source: Thorsten Meyer AI
