I usually run 3-5 Claude Code sessions concurrently on the same repo and hate juggling worktrees. So I built crew. The idea is simple: If autonomous cars don't need stoplights (supposedly), then agents don't need worktrees (or branches). crew hooks into Claude Code and injects what every other running session is doing (status, recap, last few transcript entries) into each session's context. It also lets agents message each other, landing messages in another agent's context even mid-turns. Since starting to use crew I've seen some awesome emergent behaviors: agents asking each other for reviews, delegating deploys to a single agent, and even getting lazy on account of "someone else will fix it"! Curious how others running several sessions at once handle coordination. |