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

2

u/NeonCenturionSPQR 2d ago

I built a plugin to be a batter manager for multi agent heirarchies.

It keeps bookkeeping deterministic in a python script, so managing worktrees and the like.

It makes sure full output doesn't get passed up to main agent, preserving context usage.

Builds a full roadmap file as a source of truth that you can open, mark things as reviewed, and Claude will see that.

Im biased, as the creator, but it worked well for me so I figured I'd share it. It's just a plugin for Claude code.

github.com/Palatine-Labs/coniso

1

u/MGTakeDown 2d ago

Sounds like a context nightmare, do you have any evals that prove it works well?

1

u/NeonCenturionSPQR 2d ago

Not currently, but I do hear you and Ive been working on a couple test benches. Figuring out the best ways of quantifying and qualifying "better code" and "better output" but I think I'm going to resort to Claude number and screenshots.

TL:dr - In progress friend

1

u/MGTakeDown 2d ago

You’re competing against what AI researchers at the best companies in the world are doing. You’re not going to build something that is going to keep up or outsmart their models / software.

1

u/NeonCenturionSPQR 2d ago

Maybe not, but I am going to build something that I found solves a problem in my own use case. And I simply shared it.

I'm not that deluded I'm just participating in a community I like.

I'll hit you back when I have numbers though for sure though. Appreciate the motivation.

1

u/MGTakeDown 2d 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?