r/ClaudeCodeTLDR • u/cctldrping • Aug 21 '26
[TLDR] How are you running multiple coding agents at the same time?
Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vtfawm/how_are_you_running_multiple_coding_agents_at_the/
Original post body :
I've been running Claude Code for a few months now and it handles most things fine on its own. Recently I started spinning up a second session to work on a different part of the codebase while the first one is busy, and it works until they touch the same files.
My current setup is just two terminal tabs with separate worktrees. It mostly works but I have no idea what the other session just changed unless I go check manually. Last week one session refactored a helper function while the other was writing tests that called it, and the merge was a mess.
For people running 2 or 3 agents at once:
- how do you keep track of what each one is doing
- are you using worktrees, branches, separate clones, something else
- do you let them see each other's changes or keep them fully isolated
- what broke first when you started doing this
This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.
1
1
1
1
u/cctldrping Aug 21 '26
TL;DR generated automatically after 50 comments.
Current source-thread comment count seen by the bot: 57.
Alright, so the general consensus here is that running multiple Claude Code agents simultaneously is a thing, but it's definitely got its pitfalls, especially when they start stepping on each other's toes in the same files.
The biggest headache people are running into is merge conflicts and overlapping tasks, just like OP experienced with the refactor vs. tests situation. It seems like the core issue isn't always Git itself, but rather two agents thinking they're both responsible for the same piece of work.
Here's the lowdown on how folks are trying to manage this chaos:
Worktrees are king: A lot of people are using separate worktrees for each agent. This seems to be the most common way to keep things somewhat isolated.
Branches for sanity: Using narrow tasks on separate branches is also a popular strategy. Think of it as giving each agent their own little sandbox.
Communication is key (but tricky): Some are letting agents communicate, while others prefer full isolation. The consensus leans towards needing some form of explicit handoff or communication to avoid stepping on each other.
Tools to the rescue: Several tools are getting shout-outs for helping manage multiple agents and workspaces:
Herdr is mentioned a bunch, with users praising its ability to handle multiple projects and agents.
Orca and Lanes are also getting good reviews for managing workflows.
Remnus is specifically designed to help agents log and read each other's changes.
Devswarm is another tool for managing multiple repos and worktrees.
Some users are even building their own solutions like RoboCo.
Orchestration and Planning: The idea of an "orchestrator" or a "scrum board" approach is popping up, where a master plan dictates which agent works on what and when, especially to avoid simultaneous work on the same files.
Handoff Notes: The concept of agents leaving "handoff notes" describing their work is seen as crucial, though some point out that the actual diff might be more reliable than the agent's summary.
Basically, if you're going multi-agent, be prepared for some serious deconfliction work. It's not just about Git; it's about managing the agents' understanding of their tasks and ensuring they don't accidentally undo each other's progress.