The Delegation Ladder: The Four Agentic Loops, and What Each One Lets You Stop Doing

TL;DR

Thorsten Meyer AI published a July 1 AI Dispatch that turns Anthropic’s June 30 Claude Code loop guidance into a four-rung Delegation Ladder. The framework links each loop type to a task humans can stop doing, while access, costs and broad reliability remain open questions.

Thorsten Meyer AI published a July 1, 2026 AI Dispatch that reframes Anthropic’s new Claude Code guidance on agent loops as a four-rung Delegation Ladder, a model meant to show developers and business teams how much work they can hand to AI systems without treating every task as fully autonomous.

The confirmed source chain is narrow: Anthropic’s Claude Code team published ‘Getting started with loops’ on June 30, 2026, and the Thorsten Meyer AI piece built on it the next day. According to the dispatch, Anthropic defines a loop as repeated agent work that continues until a stop condition is reached.

The dispatch identifies four loop types: turn-based Skills, goal-based /goal, time-based /loop and /schedule, and proactive workflows using auto mode. Its central claim is interpretive: moving up the ladder means the human stops doing one additional piece of work, from checking output to deciding when to stop, starting the work, and eventually writing the prompt.

At a glance
analysisWhen: published July 1, 2026; based on Anthro…
The developmentThorsten Meyer AI published a July 1 AI Dispatch reframing Anthropic’s June 30 Claude Code guidance on agent loops as a four-rung Delegation Ladder.
AI Dispatch · Insights · 1 July 2026

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 reframe
Climb the ladder and you stop doing one more piece yourself: first the check, then the stop condition, then the trigger, and finally the prompt itself. Anthropic’s own rule first: not every task needs a loop — start simplest, climb only when the work earns it.
The four loops, as rungs of delegation
↓ You drive (manual)It runs (autonomous) ↑
Turn-basedskills
You hand off the check — encode verification in a Skill so it validates its own work.
trigger: your prompt
stop: it judges done
Goal-based/goal
You hand off the stop condition — an evaluator model keeps it working until “done” is met or a turn cap hits.
trigger: your prompt
stop: goal / max turns
Time-based/loop · /schedule
You hand off the trigger — a clock starts the work; local with /loop, cloud with /schedule.
trigger: an interval
stop: you cancel / done
Proactiveworkflows + auto mode
You hand off the prompt itself — event-driven, no human in real time; orchestrates many agents.
trigger: event / schedule
stop: per-task goals
Keep the output good — the system > the loop
Clean codebase — it copies your patterns Self-verify via skills A 2nd fresh-context agent reviews Fix the system, not just the instance
Keep the bill sane — autonomy is metered
Right primitive + cheapest capable model Clear stop criteria Pilot before a big run (100s of agents) Scripts > re-reasoning · watch /usage
The take

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.”

Source: “Getting started with loops,” Delba de Oliveira & Michael Segner (Anthropic), Claude blog, 30 June 2026. Definitions, primitives & examples are Anthropic’s; the “delegation ladder” framing is the author’s. Some features are research previews. Docs: code.claude.com/docs.
thorstenmeyerai.com

Delegation Moves Beyond Prompts

For developers, the framing turns agent design into a delegation choice instead of a prompt-writing exercise. The lowest rung still begins with a human prompt, but the check can be encoded in a Skill so the agent tests its own work against a defined quality bar.

For companies, the higher rungs point to a different operating model: AI work that starts from a goal, a schedule or an event. That matters because it shifts oversight from watching every turn to setting limits, success criteria and review paths before a run begins.

AI Tools for Everyday Tasks: The Complete Beginner’s Guide To Working Smarter with AI

AI Tools for Everyday Tasks: The Complete Beginner’s Guide To Working Smarter with AI

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Anthropic’s Four Loop Pattern

The first rung, turn-based Skills, is closest to current agent use: the user asks, the system acts, checks and returns. The dispatch says Anthropic’s front-end example treats a UI change as complete only after steps such as launching a dev server, testing the control, taking screenshots, checking the console and running a performance trace.

The second and third rungs shift more control. With /goal, a separate evaluator model checks whether the task meets a defined condition or reaches a turn cap. With /loop and /schedule, the trigger is time-based; the fourth rung, proactive workflows, can start from events or schedules and may coordinate multiple agents.

“repeating cycles of work until a stop condition is met”

— Anthropic’s Claude Code team, as cited in the Thorsten Meyer AI Dispatch

Workflow Automation with Microsoft Power Automate: Design and scale AI-powered cloud and desktop workflows using low-code automation

Workflow Automation with Microsoft Power Automate: Design and scale AI-powered cloud and desktop workflows using low-code automation

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Claude Loop Access Questions Remain

Availability is still partly unclear from the source material. The dispatch says some features are research previews, and it does not establish which users can access every primitive, how cloud scheduling is governed, or how large multi-agent runs will be priced in practice.

There is also a boundary between fact and interpretation: Anthropic’s definitions, primitives and examples are attributed to the Claude blog, while the Delegation Ladder is identified by the dispatch as the author’s framing. Claims about business impact depend on how teams set stop criteria, review output and monitor usage.

The AI Prompt Playbook: Master AI Prompt Engineering with 140 Ready-to-Use Templates for ChatGPT, Claude, Gemini & Copilot

The AI Prompt Playbook: Master AI Prompt Engineering with 140 Ready-to-Use Templates for ChatGPT, Claude, Gemini & Copilot

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Teams Test One Rung

The near-term test for readers is practical: pick the first bottleneck, then choose the smallest loop that addresses it. The dispatch’s guidance is to start with simple prompting when that works, use Skills when checks can be written down, use /goal when the success target is measurable, and reserve scheduled or proactive workflows for repeated work with clear limits.

What follows is adoption and validation: developers will watch cost per run, failure modes and review burden as teams test whether loops save time without creating new supervision work.

Robotic Process Automation: Guide To Building Software Robots, Automate Repetitive Tasks & Become An RPA Consultant

Robotic Process Automation: Guide To Building Software Robots, Automate Repetitive Tasks & Become An RPA Consultant

As an affiliate, we earn on qualifying purchases.

As an affiliate, we earn on qualifying purchases.

Key Questions

What is the news event?

Thorsten Meyer AI published a July 1 AI Dispatch that reframes Anthropic’s June 30 Claude Code loop guidance as a Delegation Ladder for agent workflows.

Is the Delegation Ladder an Anthropic product?

No. The source material says Anthropic supplied the definitions, primitives and examples, while the ladder framing is the author’s interpretation.

What are the four agentic loops?

They are turn-based Skills, goal-based /goal, time-based /loop and /schedule, and proactive workflows that can start from events or schedules.

What should teams try first?

The dispatch recommends the smallest fit: a Skill when verification can be encoded, /goal when success is measurable, and scheduled loops only for repeated work.

Source: Thorsten Meyer AI

You May Also Like

Why I email complete strangers

Exploring the enduring value of emailing strangers, its impact on human connection, and how it can foster meaningful interactions in a digital age.

A Skill Is a Folder, Not a Prompt: What Anthropic Learned Running Hundreds of Them

Thorsten Meyer AI reports on Anthropic’s lessons from running hundreds of Claude Code Skills across its engineering organization.

BYD Taking Responsibility Increases God’s Eye Use & Makes Vehicles Safer

BYD now fully guarantees city driving with its LiDAR-based God’s Eye system, increasing safety and usage while assuming liability for accidents.

I stopped tracking my time. Now I can’t focus

A person who stopped tracking their time reports increased mental exhaustion and fragmented focus, raising questions about productivity methods.