Manage Multiple AI Coding Agents Without Collisions

Git worktrees, agent dashboards and vendor cloud fleets: what to own and what you can safely rent

Published 25 October 2026 Updated 25 October 2026

If you manage multiple AI coding agents in one repository, the first thing that breaks is not a bad diff: it is two agents rewriting the same file at the same moment, and one of them quietly overwriting the other's fix. The stack developers reach for in late 2026 runs from a single git flag to cross-vendor desktop command centers, and one popular board in that stack has already shut its hosted product down. Here is what each layer does, what it costs, what it needs, and which part of it is actually yours to keep.

Three agents, one file

Start with why the overwrite happens. Every agent is working in the same folder, on the same branch, so two of them can rewrite the same file simultaneously. A git worktree fixes that at the git level: each parallel agent gets its own working directory and its own branch off the same repository history, so simultaneous edits no longer corrupt each other's work.

You no longer have to wire that up by hand. Claude Code added native worktree support through a --worktree (-w) flag that runs git worktree add, creates the branch and launches an isolated session under .claude/worktrees/, with the feature rolling out through its February 2026 update cycle.

The catch is the edge of that isolation. A Claude Code v2.1.222 patch dated August 4, 2026 fixed a bug where a worktree-isolated session's sub-agents could still execute destructive git commands against the main checkout. Picture a helper agent resetting the branch you were about to ship. After the fix, isolation covers file editing and Bash across all session types, so update before you lean on it.

The practice matters as much as the flag. A Reddit user in r/ClaudeAI describes running 3-4 parallel Claude Code agents without worktrees as chaos, with agents editing the same files and duplicating work, until switching to one worktree and branch per agent plus one written task list, so no two agents own the same piece of work. That is his experience, not a benchmark, but it is the pattern the rest of this stack is built on.

Which agent is waiting on you?

Worktrees stop the collisions. They do not tell you which agent is stuck waiting for your answer while you watch another one.

Anthropic's answer is Agent View, a single CLI dashboard that lists every background and foreground Claude Code session with its state: working, waiting for input, completed, failed, idle or stopped. It shipped as a research preview on May 11, 2026. Background sessions keep running with no terminal attached, via a per-user supervisor process that starts the first time a session is backgrounded. What it needs: Claude Code v2.1.139 or later, and a Pro, Max, Team, Enterprise or API plan. The main catch is two words long, research preview, and it only watches Claude Code.

If your fleet mixes vendors, Claude Squad is the open-source route. It combines tmux, one isolated terminal session per agent, with git worktrees, one branch and directory per agent, and runs Claude Code, Codex, Gemini CLI and Aider side by side. The repository had reached 8,700 stars and 625 forks as of the research date, and it is licensed AGPL-3.0. The tool itself is free; the intelligence is not, because every agent inside still bills your own account with its vendor. Beyond tmux and git, the project doesn't list hardware requirements. Use it instead of Agent View when your fleet is not all Claude Code; don't use it if AGPL-3.0 is something your company's lawyers need to approve before it touches work code.

Notice what both tools sit on: the worktree. The dashboard only shows you what git is already keeping apart.

Where do you read the diffs?

Ten agents means ten sets of changes waiting for your eyes, and a terminal pane is a poor review screen.

Conductor, built by YC-backed Melty Labs, is a desktop app that runs Claude Code, Codex and Cursor, each in its own isolated git worktree, with a built-in diff viewer so you review changes before they merge. Pricing is Free for individuals, Pro at $50/month and Teams at $60/month per user. That price buys the app; the agents inside still run on your own model plans. The main catch is hard and unavoidable: it runs on macOS, Apple Silicon only, so Windows and Linux are out. You download it from conductor.build.

Conductor Cloud runs agents in Vercel-hosted sandboxes (8-core CPU, 16GB RAM, Amazon Linux 2023, us-east-1 region) so work keeps going without a local Mac. Convenient, but look at what just moved: your fleet now lives on someone else's machine, under someone else's business model.

What happens when the board shuts down?

Vibe Kanban is an open-source kanban board under Apache-2.0, installed with npx vibe-kanban. You drag tasks onto a board and hand each one to a coding agent. It supports 10+ of them, including Claude Code, Codex, Gemini CLI, GitHub Copilot, Amp, Cursor and OpenCode, and each task is isolated in its own git worktree. Its GitHub repository had reached 28,400 stars.

Then, on April 10, 2026, Vibe Kanban's maker bloop announced it was shutting the hosted product down, stating that since the vast majority of users were free users it could not find a sustainable business model. The tool itself continues as an open-source, community-maintained local app.

The important part is where the work was when the doors closed: in branches and worktrees in people's own repositories, because that is where the board had been putting it all along. If the board can disappear and the branches survive, which of the two were you really relying on?

Who sets your fleet size?

You may assume the number of agents you run is your decision. In the cloud, it is a line on a pricing page.

At DevDay 2026 in San Francisco on September 29, OpenAI announced Codex Cloud, which moves Codex sessions into OpenAI-hosted remote containers so tasks keep running with the laptop closed and can be monitored or continued from a phone. The Codex CLI also gained an /agents view, available from v0.159.0 onward, and it needs no configuration from you: one interface for multiple parallel sessions with color-coded status (green running, amber waiting, grey complete, red error), plus a /fork command to branch a session.

Google's Jules makes the ceiling explicit on its own usage-limits page: the free Jules plan allows 15 tasks per day with 3 running concurrently, Jules in Pro allows 100 tasks per day with 15 concurrent, and Jules in Ultra allows 300 tasks per day with 60 concurrent. Task limits reset on a rolling 24-hour window and are not shared across family-plan members. The catch is how you buy the headroom: the paid concurrency tiers are unlocked only through a Google AI Pro or Google AI Ultra subscription, not a Jules-specific plan, and that page doesn't state what those subscriptions cost.

So in the cloud the vendor decides how wide your fleet can be, and the agents run on hardware you never see.

Can one screen manage multiple AI coding agents?

Cognition is betting you will want one surface instead of three vendor dashboards. In June 2026 it rebranded its Windsurf editor as Devin Desktop, adding an Agent Command Center, a kanban-style board for managing multiple AI agents from one place, as a free over-the-air update that kept existing pricing and settings. The update costs nothing, but the announcement doesn't spell out what that underlying pricing is, so check it before you plan a team around the tool.

The part worth more than the board is the protocol. Devin Desktop supports the Agent Client Protocol (ACP), an open standard that lets any ACP-compatible agent, including Codex, Claude Agent and OpenCode, run alongside Devin inside the same editor. A Spaces feature shares context, pull requests and files across grouped agent sessions. It is still one company's editor, and you have just watched a board lose its hosted home; the open protocol is the piece that could outlive the product.

Own the worktree, rent the rest

The one layer worth committing to is the git worktree. It sits under every tool here, it is plain git that you own, and when Vibe Kanban's hosted board closed, it is what people's work was still sitting in.

Everything above it is a dashboard you can swap. If you live in Claude Code alone, use the --worktree flag and Agent View, and keep Claude Code updated. If you mix vendors in a terminal, take Claude Squad after reading its AGPL-3.0 licence. If you are on an Apple Silicon Mac and drowning in diffs, Conductor's free individual tier is the place to start. If you want agents running while your laptop sleeps, Codex Cloud or Jules will do it, as long as you accept their limits and their hardware. Whatever you pick, keep the work in branches you control: rent the dashboard, own the branches.

Sources