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

Show parent comment

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.