Run parallel coding agents with git worktrees

Launch Claude Code and Codex side by side in one room, group them by area, and give each agent its own git worktree so parallel work does not collide.

On this page
  1. 01Why parallel agents need separate checkouts
  2. 02A room is a canvas for a whole demand
  3. 03One worktree per agent
  4. 04Agents that survive a restart
  5. 05Answer from anywhere

One coding agent at a time is rarely the shape of the work anymore. A feature has a design question, a research question and a code change, and they can move in parallel. This post covers how to run several agents on one demand, Claude Code and Codex together, without them stepping on each other.

Why parallel agents need separate checkouts

Two agents editing the same working tree overwrite each other’s files and trip over each other’s half-finished changes. A git worktree is a second checkout of the same repository, on its own branch, in its own directory. Giving each agent its own worktree keeps their edits apart until you decide to bring them together.

A room is a canvas for a whole demand

In anywh, a room holds the agents that work on one demand. You launch agents into it, Claude Code and Codex side by side, and group them by area, like Design, Research and Code.

  • Shared context. Attach context to the room: every agent in it reads it, and every new agent inherits it.
  • Live cards. Each card shows what its agent is doing right now, and the agents that need you say so.
  • Mixed agents. A session can pick Codex, with its own permission modes, next to Claude Code.

One worktree per agent

Each agent can work on its own git worktree. anywh keeps that worktree until the agent’s work is integrated.

Agents that survive a restart

The agents of a room run in a host service of their own, anywh-agent-host@<profile>, next to the relay. Restarting the relay, whether for a deploy, after a crash or with systemctl restart, leaves every agent and every turn in flight running.

NOTE

Rooms need the agent host. The Linux installer sets it up. On macOS, the Homebrew relay does not ship an agent host yet, so rooms are not available there, and ordinary chats work as before.

Answer from anywhere

When an agent needs you, the card says so. Answering it from your phone is the same gesture as from your desk, which matters when the agents are running on a machine at home. Setting that up is covered in run Claude Code from your phone.

Rooms arrived in anywh 0.2. The release post has the upgrade steps, and the plan usage post shows how to watch your limits while several agents run.

All posts
anywh.sh
DocsBlogProductDownloadsPricingSign InApache 2.0 · 2026