正在加载视频...

视频加载失败

Anthropic engineers just showed how they build a full app from scratch, using a loop of agents 40 minutes from the team behind Claude Code they used three agents: one to plan, one to build, one to judge, cycling until the app actually works the winners won't have the...

1,932,261 次观看 • 3 个月前 •via X (Twitter)

39 条评论

Bonsai 🌳 的头像
Bonsai 🌳3 个月前

People are starting to learn more about Loop, looks like we’re not early anymore

Anatoli Kopadze 的头像
Anatoli Kopadze3 个月前

I think the most important thing is not to be too late.

Brohonatron 的头像
Brohonatron3 个月前

I look at this, and several of these recent Anthropic videos, and all I can think about is increased compute power, which equals money. So, you're doing something quicker, but the AI overhead cost is more than a human.

CyrilXBT 的头像
CyrilXBT3 个月前

W share bro

Anatoli Kopadze 的头像
Anatoli Kopadze3 个月前

appreciated!

echoes2099 的头像
echoes20993 个月前

majority of peeps/companies can't afford to run this

Anatoli Kopadze 的头像
Anatoli Kopadze3 个月前

That’s right

Khairallah AL-Awady 的头像
Khairallah AL-Awady3 个月前

Great share my man! Bookmarked it

Anatoli Kopadze 的头像
Anatoli Kopadze3 个月前

Appreciated

Crazyox🌶️(微微辣版) 的头像
Crazyox🌶️(微微辣版)3 个月前

三个agent循环出活,这思路真的香,回去也想试试搭一个

Rahul 的头像
Rahul3 个月前

Loops or goal Use it and be amazed 😀

Ruth Heasman 🌳🌷🦚🐉😃 的头像
Ruth Heasman 🌳🌷🦚🐉😃3 个月前

@Replit already does this.

Marv 的头像
Marv3 个月前

the judge is the real engineering problem here. plan and build can be noisy and self-correct. but the judge has to know what "done" looks like before the loop even starts. that exit condition is harder to write than the app itself.

Brook Zimmatore 的头像
Brook Zimmatore3 个月前

@grok analyze the entire agentic model in the video transcript and give an estimate of how many tokens it would cost and total $ amount estimated to do this

Cogito Ergo Sum 的头像
Cogito Ergo Sum3 个月前

This actually is not very good representation of Loop in the Video. They could have done better

Rob 的头像
Rob3 个月前

Retard

Kong Trading 🦍 的头像
Kong Trading 🦍3 个月前

Forty minutes for a full app is terrifyingly fast

/var/log 的头像
/var/log3 个月前

Learning the concept. Thanks

Springblade 🇺🇸 的头像
Springblade 🇺🇸3 个月前

Ha, I just did this exact same thing myself yesterday morning, a 4-level, 3 Developers per level perfect coding machine! and by the end of the day my Dev Loop machine and Hermes and I had a fully built and working grow room control app, with UI Dashboard and everything sending sensor readings to the database, without one single error!! Grok made me this summary: CodeSquatch is my personal AI-powered "dev team in a box." Instead of one AI trying to build software alone (which often makes mistakes), it acts like a full company development department with 4 specialized layers: Junior Devs write the first version of the code. Senior Devs review and polish it for quality. Reg Devs (Regional Developers) make sure everything fits together properly, like a manager overseeing the big picture. Master Dev does a final hardcore check, fixes anything missed, adds smart improvements I didn't even think of, and runs tests until it's rock-solid. How it works: I give it a clear description of what I want. It first creates a detailed "Master Plan" for me to approve. Only then does the team start coding in stages, with lots of peer reviews and double-checks at every step. The goal is high-quality, reliable code with far fewer errors — basically a smart, tireless team that gets better every time I use it. It's completely reusable for any project (websites, apps, tools, etc.), runs privately on my local AI setup, and saves me huge amounts of time and frustration. It's my secret weapon for building stuff faster and better. (We just finished setting it up as its own independent tool/repo so I can improve it over time and use it everywhere.) SWEET!!🤌🇺🇸

Josh Jones 的头像
Josh Jones3 个月前

Imagine that, Anthropic wants you to build loops that continuously use tokens. Weird

Danny Axelgod 的头像
Danny Axelgod3 个月前

easy when you got unlimited tokens

Onur Eken 的头像
Onur Eken3 个月前

a.k.a. burn tokens while you sleep do realize that tokens became a form of commodity, like electricity. no tokens -> no progress. it's the new abstraction of energy. which signals we're heading to a new "Tokendollar" economy. as most frontier models are US-built and proprietary. that's exactly why SOTA OSS models matter more then ever now -> fair access to tokens for everyone.

THC Humor 💹🧲 的头像
THC Humor 💹🧲3 个月前

Agent collaboration might be a bigger unlock than better models

Andrew G. Huff 的头像
Andrew G. Huff3 个月前

Loops? Hmm.

Kausik 的头像
Kausik3 个月前

New way discovered to burn more tokens, make more money, great job @AnthropicAI to keep making Software Engineering to a Bullshit Engineering. Next up, how to keep running agents forever....coming soon.

Dreamweaver 的头像
Dreamweaver3 个月前

Yes, let’s encourage people to leave high level product and critical engineering judgement to an agent that will spin its wheels using tokens till it gets it right over spending an extra 10-20mins to plan a high level product design spec with explicit logic instructions.

Steven Cheng 的头像
Steven Cheng3 个月前

the loop is the real product

James AI 的头像
James AI3 个月前

AI agents in a feedback loop will outperform AI models in isolation.

Hussain Hashim | Building SundayBack 的头像
Hussain Hashim | Building SundayBack3 个月前

@AnatoliKopadze that's wild, never thought of using agents in a loop like that. makes me wonder how many iterations it took to get something decent though

Gregor 的头像
Gregor3 个月前

not sure the judge agent holds in practice when i tried a similar loop building pennywise the judge kept greenlighting builds that broke on real data. what did they use as the termination condition?

Jonna L. Ward 的头像
Jonna L. Ward3 个月前

The judge agent is where the cost hides. Caching the plan + build context with prompt caching cut my own Claude loops by ~60% on input tokens, since each judge pass re-reads the same spec.

Voltage (Fella) 的头像
Voltage (Fella)3 个月前

The plan→build→judge loop is a brute-force pattern that compensates for weak agency by adding more agents. If the builder can't self-evaluate, bolt on a judge. If the judge rejects, cycle back. You converge eventually, but you burn 3x the context per cycle minimum. Meh.

₥AN$A 的头像
₥AN$A3 个月前

This is the way! Agentic workflows are becoming essential. My team at GroupGPT is building frameworks around similar loops. Btw, if you're into referral programs, ours pays 25% commission:

Ray 的头像
Ray3 个月前

Plan → Build → Judge → Repeat — the smarter this iteration loop gets, the more reliable the output becomes. Thanks to share an important information.

Narasimhan Rengan 的头像
Narasimhan Rengan3 个月前

Full video:

Cyberw@t 的头像
Cyberw@t3 个月前

One agent plans. One agent builds. The other agent loops your tokens until you max out your credits

Pete McCormick 的头像
Pete McCormick3 个月前

This is a fantastic share. Earned a follow :)

Alexander Menges 的头像
Alexander Menges3 个月前

What would be cool: real demo on how to use it in operation. I think loops and workflows etc is pretty clear, but how to actually set them up (event-based loop triggers, multi-agent systems etc) would be helpful :)

DimiX 的头像
DimiX3 个月前

this is exactly where coding is going. it’s no longer about individual prompt engineering, it's entirely about setting up the tightest agent loops

相关视频