riffLeaderboard

Here's what Riff found.

12 MOMENTS · YOU ARE SPEAKER A

Listen to the podcast →
Moment: Contrarian Take

dynamic workflows vs subagents

I'll let you be the judge of which one did better, but it was so close that just to save token usage, I wouldn't recommend it for something like this. What we just did, building a dynamic e-commerce website from scratch. For that, you're probably best just sticking with subagents.

00:00
From 710s
Moment: Framework

dynamic workflows vs subagents

With subagents, Claude has to personally loop through all 150 of those tasks, whereas dynamic workflows, that takes that whole plan out of Claude's head and writes it down as code.

00:00
From 141s
Moment: Quotable Line

Opus 4a dynamic workflows

But is that really true, or is this just another token-guzzling cash grab?

00:00
From 10s
Moment: Concrete Number

e-commerce store build scope

There are 30 products that each need a name, a description, a photo, price, SEO copy, all of that. That's like 150 jobs before we even touch the cart or the checkout or anything like that.

From 131s
Moment: Counter-Intuitive

dynamic workflows token usage

Looking at other demos on Reddit and X, it seemed like people were really maxing this out quickly, like literally one prompt. But it was examples like refactoring a codebase or migrating entire codebase. So I tried to get to an example where it was super token intensive, but we only got about 13% use there.

From 427s
Moment: Honest Admission

Playwright QA agent behavior

That is just crazy that it was running Playwright for like 20 minutes. What was it doing? What was it seeing?

From 699s
Moment: Process Detail

dynamic workflow execution model

A dynamic workflow is a JavaScript script that orchestrates subagents at scale. Claude writes the script for the task you describe, and a runtime executes it in the background while your session stays responsive. So Claude is just writing that script one time. That's all the work that this main Claude parent agent needs to do, and the rest is just handled by the script.

From 153s
Moment: Story

multi-agent design debate

Okay, so these agents are talking to each other. Okay, that's kind of cool. So it's proposer A comes up with something. Proposer B came up with another angle. Proposer C, another angle. And then we have critics that are critiquing the different proposers. Weak, weak, weak critic. And then design synthesizer. This might be all over the place. There's probably too many cooks in the kitchen.

From 375s
Moment: Tactical Advice

when to use dynamic workflows

The only time this is really worth it is when you're dealing with a massive codebase, at least in the demos I've seen online, a migration or doing a huge refactor or anything like that could prove worth it with dynamic workflows.

From 722s
Moment: Industry Context

Anthropic token limit policy

This is Anthropic probably being generous about their tokens as well, but about usage with this new model being released, they'll probably start to crack down on this a bit.

From 441s
Moment: Personal Philosophy

dynamic workflows for knowledge work

I also mentioned knowledge work in my Opus 4.8 review video and after this test, I don't think that's where dynamic workflows shines either. Regular subagents, unless you're parsing some massive spreadsheet, are probably just fine.

From 733s
Moment: Quotable Line

AI-generated product copy quality

Aged leather and white oak open with quiet authority. Do the confidence work while you find your mute button. Don't know what that means.

From 506s