Anthropic's Dynamic Workflows: What Everyone Gets Wrong!
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
AI News: Everyone's Leaving ChatGPT!
Matt Wolfe
54.4k views
Everyone Hates Starfleet Academy - It Gets Worse
Nerdrotic
368.5k views
Anthropic confirms software engineering is NOT dead
ThePrimeTime
341.6k views
What Big Tech Still Gets WRONG about Great Programmers | Casey Muratori
A Life Engineered
92.5k views
Sonnet 4.5 Is Here—And It’s a Beast at Coding
Prompt Engineering
52.0k views
GPT-OSS Jailbreak with this Simple Trick
Prompt Engineering
54.4k views
What is AI Engineering
Telusko
67.6k views
Context Engineering is All You NEED!
Prompt Engineering
38.7k views
Gemini CLI — Google’s Free Open-Source Coding Agent
Prompt Engineering
56.6k views
AI prompt engineering in 2025: What works and what doesn’t | Sander Schulhoff
Lenny's Podcast
68.3k views
Top Comments (9)
When Kimi came up with their agent swarm thing I immediately thought of multi core CPUs, it is a good thing but most tasks require some form of sequence to be followed it takes a lot of effort to split tasks for a process into individual tasks most of the time and it will produce overhead, and in this case it will burn a lot more tokens for small gains
Thank you for the explanation. Its becoming hard to track all these new developments.
I ran this on one of my coding benchmarks and you are right it can burn through the tokens like crazy.
great video, thanks!
"The workflow completed — 23 agents, ~2.8M tokens, all 11 subsystems mapped and adversarially verified. The full brief is in the output file (truncated in the notification). Let me read the complete result so I can write it to the MD file accurately."
So this is why Claude has been down all day and all night (on and off)... What was Anthropic thinking, too confident in its GPU cluster? This is highly inefficient, impossible to get solid result and makes it very hard to check the work at least for the models' current capabilities (but the concept will soon be possible) however the inference usage on this system is just grotesque.
Anthropic doing anthropic thing. Making us tokenmax.
okay, so
Yeah I don't need it.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (9)
When Kimi came up with their agent swarm thing I immediately thought of multi core CPUs, it is a good thing but most tasks require some form of sequence to be followed it takes a lot of effort to split tasks for a process into individual tasks most of the time and it will produce overhead, and in this case it will burn a lot more tokens for small gains
Thank you for the explanation. Its becoming hard to track all these new developments.
I ran this on one of my coding benchmarks and you are right it can burn through the tokens like crazy.
great video, thanks!
"The workflow completed — 23 agents, ~2.8M tokens, all 11 subsystems mapped and adversarially verified. The full brief is in the output file (truncated in the notification). Let me read the complete result so I can write it to the MD file accurately."
So this is why Claude has been down all day and all night (on and off)... What was Anthropic thinking, too confident in its GPU cluster? This is highly inefficient, impossible to get solid result and makes it very hard to check the work at least for the models' current capabilities (but the concept will soon be possible) however the inference usage on this system is just grotesque.
Anthropic doing anthropic thing. Making us tokenmax.
okay, so
Yeah I don't need it.