This is cool, but does everybody have enough work for multiple agents in parallel?
I feel like I'm limited by writing specs for agents, then by reviewing their work.
I typically spend 30-60 minutes writing a spec, then the agent runs for 30-60 minutes, then I spend 30-60 minutes refining code/ui/etc before putting up a PR, then another 30-60 minutes waiting for CI + addressing automated + human code review feedback.
I find if a project is made with agentic coding in mind, you can try to implement features as they come to mind and bounce between different CC terminals.
The problem is that this is true of none of my work projects and the onboarding cliff to agentic coding is quite steep. I have to use discretion to apply CC when it does make sense, which is not that often.
I'll have claude code editing a script on my laptop and another on the VM running it and synthesizing the results. Then sometimes I'll have another doing some odd job or researching something. Then I'll pull up gemini in my browser to figure out what I should make for lunch...
If you can context switch then you can pipeline
I usually use one instance, sometimes two. But this is a reasonable account of Chris Rackaukas using 32 instances at a time to do boilerplate maintenance across a bunch of open source repositories: https://www.stochasticlifestyle.com/claude-code-in-scientifi...
> I have had to spend like 4am-10am every morning Sunday through Saturday for the last 10 years on this stuff before the day gets started just to keep up on the “simple stuff” for the hundreds of repos I maintain. And this neverending chunk of “meh” stuff is exactly what it seems fit to do. So now I just let the 32 bots run wild on it and get straight to the real work, and it’s a gamechanger.
Boris who created Claude Code has a multiple clauses setup it seems as daily usage https://x.com/bcherny/status/2007179832300581177