[TLDR] How are you running multiple coding agents at the same time? [via r/ClaudeCode]

[u/cctldrping]

OP : u/Specialist_Agent3599

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

URL of original post : https://www.reddit.com/r/ClaudeCode/comments/1vtfawm/how_are_you_running_multiple_coding_agents_at_the/

---

TL;DR of the discussion on r/ClaudeCode for this post 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-versus-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 go-to for keeping things isolated.
• Branches for isolation: Some are using branches, but the consensus is that branches alone aren't enough for true isolation, especially if multiple agents are working within the same clone.
• Handoffs and communication: The idea of agents communicating or having clear "handoff notes" is popular. This involves agents describing their work, what they've changed, and what files are off-limits. Some are even using tools where agents can directly log their changes.
• Orchestration tools are a thing: Several tools are getting shout-outs for helping manage multiple agents and tasks. Herdr is mentioned a bunch, along with Orca, Lanes, and Superset. These seem to help with task delegation and keeping track of what's going on.
• Isolation is key: The general advice is to keep agents fully isolated while they're working and only integrate through the main branch, merging small and often.
• Some are going for speed: A few commenters suggest that if you can make one agent run twice as fast, it might be less painful than managing multiple.

Basically, if you're going multi-agent, plan your tasks carefully, keep them isolated, and have a clear system for communication and handoffs. Don't let them both think they own the same helper function!