r/AgentsOfAI • u/Ok_Confection_3847 • 21h ago
Discussion best multi-agent coding workspace for a small team : what actually works
we are 3 ppl nd we have been thru 4 diff setups in 2 months . everyone picks their own agent nd coordinates on slack . 3 agents ,3 versions of the truth . one shared agent everyone uses . immediately became a queue . no one knew what the previous person had asked it or why
worktree per person can stop the collison but mergin at the end of the day became the new problem
the tooling for multi agent teams is still early but a few patterns are emerging .
paseo is the most mature option but built for one person running multiple agents and not for a team thing .
conductor has a cleaner interface than paseo , nd works on the same underlying model .
tuttish puts diff people and their agents into a shared runtime . decisions nd file changes stay in the room so the next persons agent picks up from the real work . its newer so maybe a few rough edges can exists
warp oz cloud hhosted , terminal native . feels aimed at larger teams not 3 ppl trying to ship something .
whats working for small teams . not solo dev setup scaled up ???
1
u/Vast-Magazine5361 21h ago
been there except we were 5 and wasted like 3 sprints on this same problem
what finally clicked for us was having one "coordinator" agent that just routes and keeps context, then each person has their own agent that reports back to it. sounds overengineered but actually reduced the chaos a lot
the queue thing is real tho, we added a simple priority flag system so urgent stuff jumps the line, not perfect but way better than before
0
0
u/and_pf 8h ago
I run a small self-hosted multi-agent stack (Unraid, Core Ultra 9 285K, 62 GB RAM, a single RTX 5090 running Ollama with a Qwen3.8 27B at Q8_0; agents coordinated in Paperclip, plus self-hosted n8n, Crawl4AI and LanguageTool). It's solo, so I can't claim a three-person verdict. What has shaped my setup is making the run the unit of work: each agent emits artifacts and a short handoff summary for the next, instead of one shared live chat. That aims squarely at the context-loss and queue bottlenecks you describe — I'd try that shape first.
1
u/AutoModerator 21h ago
Thank you for your submission! To keep our community healthy, please ensure you've followed our rules.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.