Video wird geladen...
Video konnte nicht geladen werden
Anthropic engineer: "Stop re-prompting Claude all day. Build the loop once. Let it do the work." 00:00 - Build your first autonomous agent 05:02 - Make the loop fix its own mistakes 16:43 - Give Claude memory across sessions Prompting is the old workflow. Loops are the new one.... show more
320,138 Aufrufe • vor 3 Monaten •via X (Twitter)
42 Kommentare

build the loop once, give it memory, let it fix its own mistakes. most people are still stuck re-prompting because they never built the first loop

memory is what turns a loop into a compounding system

A good loop turns Claude from something you repeatedly instruct into something you actually operate. That’s a much bigger shift than better prompting

prompting gets answers loops get work done

Tired of re-prompting Claude all day - just build the loop once and let it run. Self-correction + memory = magic

the loop is the product prompting is just the interface

How does the loop decide it actually fixed the mistake?

by testing the outcome against explicit success criteria not by trusting its own confidence

loop engineering has taken over AI incredibly quickly

because prompting was never enough for reliable work

loops are only an upgrade when the stop condition is trustworthy. otherwise you’ve just automated re-prompting and made the mistakes more expensive

the self correction step is where loops become useful or expensive

self correction is the difference between automation and automated mistake

Check out Fractal for recursive graphs of looping agents:

loops still break at 3am

the real test is who fixes the loop at 3am

its already legendary tlak

already feels like one of those talks people will reference for years

I follow all het lecture for real

same her lectures are always worth the time

Sounds great in theory but it doesn't fucking work. You have to keep telling it what to do even after it repeats the same mistakes and then it says you are right for calling it out on its mistakes.

But are we sure that the loop system that is built by AI using memories can handle any unknown learning captured during the loop, that may require us to change the whole flow and move in a new direction now?

Building the loop once beats re-prompting all day.

@PhotonStarling

Every repetitive task is a candidate for an autonomous workflow. That's where businesses save time and money.

most people are still babysitting the model. the real unlock is giving it a loop and getting out of the way.

Build the loop once, let it do the work, simple but true

build once let it learn

I am gonna stick with manual flow for now, I like the flexibility to be able to guide the AI on a detailed level

the day my loop started catching its own mistakes I stopped opening the terminal every ten minutes everything before that was just fast typing honestly

okay, thanks for sharing

I found a reason to live

Awesome

loop engineering > prompting

Exactly. The real unlock is designing the loop to self-correct — most people stop at the first success and miss the long-term stability. Curious: do you find memory across sessions adds more reliability or just more complexity?

hey write state they cannot safely undo

Loops are the right unit. The next layer is scoped permissions and audit trails, so agents can run real tasks without each step needing a human in the chair

loops over re-prompting is the whole shift in one line. saved

I would but I got less tokens than bitcoins

Loops are just the start. Workflows need hubs to branch to different models, control gates, merge gates and so much more to get reliable results without human approvals.

30 min for build + self-correct + memory, curious how much of that survives a real production case

现在的 workflow 确实都在往 Agent 方向转,之前写自动化脚本处理运营数据时,一直卡在单次 Prompt 的逻辑闭环里,这种带 Memory 的 Loop 才是真正的生产力。
