Early OpenClaw contributor reveals the token cost tradeoff of AI sub-agents

But, yeah, I I think we should lean towards going towards, like, sub agents just so the main thread is always, like, quick to respond.

28:19 / 28:57

Is that gonna be automated? This like, shouldn't it know to just

every request on a sub agent? Yeah. Some people don't really want it because, once again, you're using more tokens when you do create a sub agent a sub agent because, I mean, it has to recreate, like, the the memory the prompt and memory and stuff, so it was 20,000 tokens. But, yeah, I I think we should lean towards going towards, like, sub agents just so the main thread is always, like, quick to respond. Yeah. This seems to me like the,

inevitable architecture. We have Mac Studios on order. I understand there's a new Mac Studio coming that's gonna be designed natively

About this clip

An early OpenClaw contributor discusses the architectural decisions around AI sub-agents, explaining why some users resist automation due to increased token costs (20k tokens per sub-agent). The conversation touches on the inevitable shift toward sub-agent architecture for better main thread responsiveness.

Why this clip

Provides inside perspective on real architectural tradeoffs in AI agent systems that other developers are likely facing.

28:19 - 28:5738stechnical insight

Share

LinkedInX

More from this episode

Similar clips from other shows

From the blog

Want clips like this for your podcast?

We find your top 5-8 clips, write the hooks, and deliver ready-to-post content. First 2 episodes are free.

Get 2 Episodes Clipped Free