{"version":"2.1.221","anchor":"forked-background-sessions-get-clearer-worktree-guidance","canonical_anchor":"forked-background-sessions-get-clearer-worktree-guidance","heading":"Forked background sessions get clearer worktree guidance","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221\/e\/forked-background-sessions-get-clearer-worktree-guidance","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.221","markdown":"### Forked background sessions get clearer worktree guidance\n\nForked background sessions are told to stay in their own worktree and never touch the original session's branch.\n\n**What**\n\nThe system prompt appended to a forked session that keeps the parent alive was rewritten to be explicit about isolation.\n\n**Details**\n\n- names the tool to use for isolation\n- tells the fork never to enter the original session's worktree and explains why not to check out the original's branch\n- adds a new \"own-worktree\" case for forking out of the user's own checkout\n- the line is skipped if the same text is already present in appendSystemPrompt\n- only added for forks that keep the parent session alive\n\n**Evidence**\n\n`so your edits don't land where the original session is editing.`\n\n- Area: Sessions\n- Names: `appendSystemPrompt`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}