there are four types of agent loops. most people only know one.
loop engineering is a choice between four structures, each handing off one more job than the last.
every one answers two questions: what starts a run, and what ends it.
hand-run, you answer both yourself, every time.
1) turn-based
→ you prompt, it acts, you review, you prompt again. both jobs stay with you.
use when requirements are still forming.
2) goal-based
→ "/goal hit Lighthouse 90, stop after 5 tries." an evaluator checks, a no sends it back.
use when the outcome is measurable but the path isn't.
3) time-based
→ a clock fires, it runs "check the PR, fix CI," then waits. /loop local, /schedule survives a closed laptop.
use for recurring work.
4) proactive
→ no human present. it watches a channel, spawns triage, fix, and a reviewer, closes the task itself.
use for standing duties you can't predict.
not which one is most advanced.
whether your task is exploratory, measurable, recurring, or standing.
the more you hand off, the less you babysit.
full breakdown in the article below.
Anthropic team:
"More than 40% of code at Anthropic is already written by agentic loops.
The target is 80% within 6 months."
An agentic loop is simple:
Plan → Act → Verify → Repeat.
Plan: read, grep, think
Act: write, edit, bash, MCP
Verify: test, build, logs
In this 30-minute talk, Anthropic breaks down the exact workflow behind modern coding agents.
This one explains agents better than 100 setup tutorials.
Watch it today, then read the full framework below.
Anthropic just dropped 5 workshops, revealing the latest capabilities of Fable 5:
• 00:00 - deep look into Fable 5
• 11:22 - Fable 5 and the capability curve
• 30:54 - building managed agents with Fable 5
• 44:29 - real use cases of Fable 5 by teams
• 57:43 - how to deploy agents with Fable 5
These 1-hour of sessions will replace 100 articles on how to actually use Fable 5.
Watch them today, then read the best practices from the sessions in the article below.