squaresinger's point matches what I've found. Once three agents are going, you become the coordination point - you're holding the plan and reviewing all of it, and that part doesn't scale the way the generating does. What's kept it manageable for me is treating each one like an intern on a single, well-specified task I can check before it moves on, rather than running a swarm and hoping it converges. Wrote this up here: https://prickles.org/tenet/the-intern-pattern/AI1
this post was submitted on 25 May 2026
21 points (88.9% liked)
Programming
27046 readers
120 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
Is anyone actually productively running multiple agents at once? All the context switching in such a short time span feels like a great way to completely forget what you are doing and losing tasks in the mess.
Multiple top-level agents can't modify the same codebase simultaneously, they'll confuse each other. But you can instruct the main agent to spawn sub-agents that it coordinates for you, to increase throughput and reduce token consumption.
No but you can lie to yourself that you are.
I am getting in the habit of keeping one async agent going in the background working on things while I also use ai in windsurf.
I think windsurf supports this natively with their background agents, but I run my background task in Claude code because then I can use my local qwen 3.6 27b
What does this parallel work mean? Does the background agent work on the same codebase as you? Doesn't that cause conflicts and confusion?
Nah I typically have it doing something else. And every 15m or so I toggle back and do next step.
Quite often Sysadmin stuff too. I have it do ansible for my pi cluster, and general cluster maintenance like check backups, troubleshoot services, create a firewall rule, etc.
I’ll also ask it research style stuff, like “check out ram usage of ai-1 box and lmk if cache is big enough for 5 concurrent full contexts. If not, change the recipe and restart it. “
But what for? Just to burn your employer's tokens to teach them that AI is a waste of money? (I mean, I'd respect that.)
I am self employed. I do it because it allows me to do my work in less time, or do more work in the same amount of time. Sometimes I’m having it do little personal projects in the background.
$20/mo for a windsurf sub. Plus like I said, I run qwen 3.6 locally (free) and get very productive output, and that’s also private, which is the main reason I invested in hardware.
AI code is pretty unusably bad for long term use anyway https://medium.com/@dumaysacha/i-saw-the-horror-of-ai-and-coderabbit-ai-did-too-a09622ac85de so best solution is to just to handwrite proper code as before. It's not like we ever had much of an output problem in most coding industries, it was always a quality and bugs problem.
Can you maybe post the text.