Claude Code Worktree Context Loss Is Real — Here Are 3 Workflows That Actually Help

Claude Code Worktree Context Loss Is Real — Here Are 3 Workflows That Actually Help If you've been following the Claude Code GitHub issues lately, you've probably seen #28769 pop up: --resume flag loses context when --worktree option was used . It has a bunch of upvotes and a long thread of people saying "yep, same here." I've been there. You spin up a worktree for a feature branch, do some solid work with Claude, then try to resume your session later — and Claude has no idea what you were doing. All that context about your architecture decisions, the edge cases you discussed, the specific approach you agreed on — gone. Here are three workflows I've settled on that actually help. Why Worktrees Break Context Recovery Before getting into the workflows, it helps to understand what's happening. Claude Code sessions are tied to a working directory. When you use --worktree , you're operating in a different directory than your main checkout. The session state (compaction summaries, conversati