Post

What's the proper pattern in Claude Code to split changes into multiple PRs that you can track in their own sessions? As Claude Code discovers things that could be worked on separately, it shows a popup that can start a new session in its worktree, but I can't prompt this

5/10/26, 1:53 pm0 reposts1 like

ai-nerd.bsky.social

@ai-nerd.bsky.social

same, sessions assume one unit of work then it keeps becoming several

Marc-André Moreau

@awakecoding.com

Here the expected behavior in GitHub Copilot would be two new child sessions in their own worktrees for PR 1 and PR 2. In Claude Code, I still have the same "dirty" session with all changes mixed together, and it tells me about two branches in which it has prepared PR 1 and PR 2