Summarizer

Git Worktrees Parallel Development

← Back to Claude Code On-the-Go

The adoption of Git worktrees for parallel development is fundamentally transforming the developer workflow into one of "agent orchestration," where AI tools like Claude can autonomously tackle multiple tasks across different branches simultaneously. While many users rely on specialized wrappers like Conductor or custom containerized environments to mitigate the complexity of worktree setup, the prevailing sentiment is that this configuration unlocks massive productivity by allowing developers to cycle through agents as they review code and update project memory. However, some remain wary of this "always-on" culture, highlighting the cognitive strain of constant context switching and the practical challenges of verifying AI-generated code without a robust, local testing environment. Ultimately, this shift suggests a future where high-throughput coding depends as much on sophisticated orchestration tools as it does on a developer's ability to manage multiple parallel streams of logic.

6 comments tagged with this topic

View on HN · Topics
I've been using git worktrees with Claude and it's pretty awesome: https://www.youtube.com/watch?v=up91rbPEdVc Pair worktrees with the ralph-wiggum plugin and I can have Claude work for hours without needing any input: https://looking4offswitch.github.io/blog/2026/01/04/ralph-wi...
View on HN · Topics
Worktrees took way too much setup and hand-holding for me, but https://conductor.build made it easy!
View on HN · Topics
I delayed adopting conductor because I had my own worktree + pr wrappers around cc but I tried it over the holidays and wow. The combination of claude + codex + conductor + cc on the web and claude in github can be so insanely productive. I spend most of my time updating the memory files and reviewing code and just letting a ton of tasks run in parallel
View on HN · Topics
I've been working on something similar: https://github.com/shepherdjerred/monorepo/tree/main/package... Essentially you run a server on some machine. Sessions are created in Docker containers, K8s pods, or via Zellij (an app similar to tmux). You can: - Directly attach to sessions via Docker attach (built-in via a TUI). You get a normal Claude Code experience, but multiplexed. The switcher/UI shows you the status of Claude and the PR (pushed, merge conflicts, CI status, review status, etc.) - Manage sessions via a web UI. Connect to Claude Code directly via your browser. You have access to the usual Claude Code terminal or a native chat view. - Manage sessions via an app. You have access to a native chat view. It achieves isolation via Git worktrees + a proxy so that containers have access to zero credentials (there aren't even any Claude code creds in the container), which allows you to more safely use bypass all permissions mode. This works better for me that Claude Code on Web because I have control over the environment Claude is running in. I can give it any Docker image I want, I can have it connect to my local network, etc. It's still a WIP (the core bits are there, but it's not polished yet), but I'm hoping it provides a friendlier UX with a similar goal for what the OP has in mind.
View on HN · Topics
This is a bit too "plugged in" for my liking. If I am in line for coffee, it's usually respite away from work, not an opportunity to do more. However, I do love the tmux + worktree + claude setup. I use this now and I know a few peers who do too and it's very enabling. This is what work feels like these days: cycling through agents, each working on a task, checking their work, unblocking them.
View on HN · Topics
This sounds cool but I feel like I need to often run the code in one way or another when verifying what Claude does. Otherwise it feels like driving blind. Claude Code already has the web version which I could use from my phone and fair it can't run scripts etc which limits the output quality. But if I can't verify what it did it also limits how long I can let it run before I need my laptop eventually. Ofc if you have demo deployments etc on branches that you could open on mobile it works for longer. Another issue is that I often need to sit down and think about the next prompt going back and forth with the agent on a plan. Try out other product features, do other research before I even know what exactly to build. Often doing some sample implementations with Claude code and click around these days. Doing this on a phone feels... limiting. I also can't stand the constant context switching. Doing multiple feature in parallel already feels dumb because every time I come from feature B to A or worse from feature G to E it takes me some time to adjust to where I was, what Claude last did and how to proceed from here. Doing more tasks than 2 max. 3 in parallel often ends up slowing me down. Now you add ordering coffee and small talk to the mix and I definitely can't effectively prompt without rereading all history for minutes before sending the next prompt. At which point I might have also opened up my laptop. Ofc if you truly vibe code and just add feature on feature and pray nothing breaks, the validation overhead and bar for quality goes down a lot so it works a lot better but the output is also just slop by then. I typed this on my phone and it took 20 minutes, a laptop might have been faster.