For heavier work I run a few Claude Code sessions at once, each on its own worktree. Herding them got old
Tried GUI orchestrators, tmux setups, and Claude Code's own agent teams, but none quite fit how I work
All I want is to hand off a task from the session I'm already in, ok the plan, and let the team split it across worktrees and review each other before anything merges, without me babysitting them
So I built cc-huddle, a small native Claude Code plugin
https://t.co/2JmxrOul4Z
@Paneherd Only its own branch, and that's fine. Two people on a team also find the overlap at merge. Whoever merges second resolves it. Here it's the author of the later delivery, in their own session, and the result gets reviewed again.
@clementrog Two people on a team hit the same conflict at merge too, that's just git. Whoever merges second resolves it. Here it's the author of the later delivery, in their own session, and the result gets reviewed again.
@matteo_titta Same, until I started splitting the work with parallel runs in mind. Each agent stays inside one task with a clear output, and the review only checks the criteria we agreed on upfront