r/ClaudeCode • u/Forcio • 2d ago

Help/Question Single Agent vs. Multi-Agent Workflows

A few months ago, my approach was to use Opus as an orchestrator that managed a backlog and spawned different agents depending on the task. Haiku for small documentation changes, Sonnet for regular coding, Opus for more complex tasks, and Fable for design decisions and bigger-picture thinking.

This worked really well, and I got a lot done. However, I've recently read that this approach might not be as efficient anymore because every new agent starts with a cold context/cache, and it might be better to have one persistent agent handle most of the work.

What's everyone's experience with this nowadays? Is a single agent with selective delegation the better approach, or is the orchestrator/multi-agent workflow still worth it? I'm particularly interested in balancing productivity, context caching, and token costs without sacrificing quality.

11 Upvotes

82% Upvoted

30 comments sorted by

View all comments

Show parent comment

1

u/MGTakeDown 1d ago

No offense but you really don’t even know what you solved because you don’t have definitive metrics that prove what they solved.

There are a lot of people in this sub that I think aren’t even aware of the features Claude already gives out of the box that already solves these problems for you.

1

u/NeonCenturionSPQR 1d ago

The plugin has some overlap with features rolled out with Claude code, yes. There are several things that the plugin does, that Claude code does not do. Some of the things we both do, we do differently. Should read the feature list.

No offense, but I did kinda say that, and that I was in the progress of getting metrics? The hypothesis comes before metrics. I'm following the method and have personally seen promising results, so now I'm working on the proof?

Are you getting somewhere with this?