your agent loop needs 8 exits. most people ship only one.
(explained with triggers)
1) goal met
→ an evaluator scores the output against a rubric, and the run stops on a pass.
→ fires when the work is measurably done, not when the model says it is done.
2) turn cap
→ a hard ceiling on iterations, counted and enforced by the harness, not the prompt.
→ fires on the task it was never going to finish, before you pay to find that out.
3) budget cap
→ a limit on tokens or dollars, whichever one runs out first.
→ fires mid-run, which is exactly why it is the exit that saves you the 3am bill.
4) wall clock
→ a deadline on elapsed time, independent of how much progress was made.
→ fires when the run collides with a deploy window or the start of business hours.
5) no progress
→ hash the state every turn and compare it against the last few.
→ fires when three turns in a row change nothing. busy is not the same as moving.
6) human interrupt
→ an approval gate before risky steps, plus a kill switch that lives outside the loop.
→ fires whenever you decide, and it is the one exit the model cannot argue with.
7) error threshold
→ a counter of consecutive failures that resets on any success.
→ fires at n in a row, so it halts instead of retrying into the same wall all night.
8) external event
→ a webhook or a poll on whatever the task was actually about.
→ fires when the PR merged or the ticket closed and the work stopped mattering.
a loop with one exit hangs. a loop with eight is a system.
write the exits before you write the prompt.
Andrew Ng just released a 1-hour course on building agentic knowledge Graphs from scratch:
• 00:00 - Introduction to agentic knowledge Graphs
• 03:07 - Construction of agentic Graphs
• 14:00 - Architecture of multi-agent systems
• 23:00 - Building agentic graphs with Google ADK
• 01:06:03 - Why Graphsare the future of agentic AI
Worth more than 10 articles on loop engineering.
Watch it today, then read how to become a graph engineer in the article below.
el ingeniero que construyó Claude Code acaba de publicar un video de 28 minutos sobre cómo escribir prompts que realmente funcionan
he visto cursos de 300$ que no cubren lo que él muestra en los primeros 10 minutos
archivos CLAUDE.md, atajos de memoria, sesiones paralelas, patrones de prompting
todo en un video y completamente gratis
funciona seas desarrollador, principiante o alguien que lleva meses usando Claude
NVIDIA CEO, Jensen Huang:
"Nobody writes prompts anymore. The new job is to write and handle loops."
This is the shift that's going to define the rest of 2026.
53 minutes of pure insight from one of the richest men on earth.
Watch it, then read the full guide on how to actually use loops below.
Today we're shipping screen-aware dictation.
First, we built a speedy speech-to-text (very fast, ~450ms).
But, many products do this!
So we went further. Now dictate using your screen as context. In Claude Code, it writes the prompt. In G-Mail, it replies in your voice.
Demo:
What’s the harshest truth every young man must eventually learn?
“Everyone is always rooting for you.
Your parents want you to be a great son.
Your wife wants you to be a great husband.
Your boss wants you to be a slam dunk hire.
Every first date you’ve ever been on they’ve been rooting for you to get laid.
Every time you started to tell a joke people hoped it would have a hilarious punch line.
Your proximity to anyone is a reflection of themselves, meaning the deck is never stacked against you, and your failures are completely your own.” — @AdemLuz
6 months of Claude Max 20x, on us.
We're expanding Claude for Open Source to more of the community.
If you're a maintainer, a core contributor, someone landing PRs across the ecosystem, or someone keeping a critical package alive, apply today!