In my last post, I wrote about building Pockode to control Claude Code on my home PC from my phone.
After using it for a while, the next pain point became clear: parallel work.
When you're using Claude Code, the waiting time starts to feel like a waste.
Pockode's worktree switching feature
So I added git worktree management to Pockode.
A few taps in the sidebar, and you can create and switch worktrees.
Pockode was designed mobile-first, but I use it on my PC all the time too.
By focusing on making switching "as easy as possible" on mobile, it ended up being the smoothest workflow on desktop as well.
More and more tasks I want to run simultaneously
While Claude Code is working on one feature, other things keep popping into my head:
- I want to push forward on another feature
- I want to investigate a bug
- I want to clear out the PR review backlog
Back when I was writing code by hand, I'd just do things one at a time. But with Claude Code, the urge to "have it do multiple things at once" comes naturally.
The question is: how do you manage parallel work?
Running in parallel in the same directory leads to collisions
If you run multiple Claude Code instances sharing the same working directory, things will go wrong:
- Files being generated get overwritten by another task
- Changes from one task break the assumptions of another
- State keeps shifting, and you lose track of what's actually done
You can make it work if you're careful, but if parallel work is the norm, you have t
Original text: https://sijiaoh.com/en/posts/pockode-git-worktree-parallel-workflow/
Top comments (0)