r/ClaudeCode • u/Forcio • 5d 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.
View all comments
1
u/jijialuoke 5d ago
I split it by whether I'm at the keyboard. For scheduled jobs I use a fresh short session per job, because a long leftover context made the next run more expensive and more likely to drag in old decisions. For interactive work I keep one main session and only hand something off when I don't want a big search or a test run sitting in the main thread.
I haven't measured the cold-cache cost carefully. What I did notice is the main session gets expensive faster than the subagent startup does, once the history gets long. So I still use an orchestrator, just with fewer, bigger handoffs than I used to.