Claude Code v2.1.221 ·
Forked background sessions get clearer worktree guidance
Forked background sessions are told to stay in their own worktree and never touch the original session's branch.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
0Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.221,
ImprovementsSection of the release
What
The system prompt appended to a forked session that keeps the parent alive was rewritten to be explicit about isolation.
Details
- names the tool to use for isolation
- tells the fork never to enter the original session's worktree and explains why not to check out the original's branch
- adds a new "own-worktree" case for forking out of the user's own checkout
- the line is skipped if the same text is already present in appendSystemPrompt
- only added for forks that keep the parent session alive
Evidence
so your edits don't land where the original session is editing.
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.221 →
