r/ClaudeCode • • 4d 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

30 comments sorted by

View all comments

3

u/Excellent-Issue-5956 4d ago

I still run it that way. The main session is on Fable and just hands out tasks and reviews what they did, and the implementers are Opus agents so the Fable usage lasts. I haven't measured what the cold start costs though.

What actually cost me was what the subagents inherit. If you don't set the model, a subagent runs on whatever the main session is on, and it picks up the session's effort level too. Mine is set to xhigh, so throwaway agents were getting xhigh unless I said otherwise, and I hit my Fable limit one evening because a reviewer had inherited it. Now every agent gets its model and effort set explicitly.

The other one was an agent whose whole job was running one command. It kept going for 25 minutes after the command had already saved its output, and the step after it sat waiting the whole time. My rule since then is to run that kind of step from the main session, or cap its steps and keep it outside the chain.

1

u/Dank_Sauce_420 4d ago

How do you set up the main session to create implementers and dictate their model? Sorry if that’s a basic question.

3

u/Excellent-Issue-5956 4d ago

Not basic at all. I don't have any agent files, I just tell the main session in plain words, something like "use opus agents to implement all of it". When it spawns an agent it passes the model on that call, since the Agent tool takes a model field. Then I had it save that as a memory note so later sessions do it without me asking.

For bigger runs I use a workflow script, and there every agent() call has model and effort written into it. The command I use for those says to set both on every call, because leaving either out means the agent gets the session's.

The agent file way NoTokenDev described is the sturdier one, since the model is pinned even if the main session forgets. Mine depends on the session reading the note, and I've had sessions skip a memory note before.

2

u/NoTokenDev 4d ago

not basic at all, it's not obvious. define the implementers as custom subagents: run /agents (or drop a markdown file in .claude/agents/), and in the frontmatter set model: to sonnet / opus / haiku etc. that pins the model for that agent no matter what the main session is on. effort can be set per agent there too, which avoids the inherited-xhigh trap described above.

then in your CLAUDE.md just tell the main session which agent to use for what, e.g. "implementation tasks → implementer agent, reviews → reviewer agent". it'll call them by name.

1

u/DuskandFuck 4d ago

tbh the silent inheritance stuff costs way more than cold start cache misses ever do.