{"version":"2.1.257","anchor":"forked-background-sessions-get-an-explicit-worktree-warning","canonical_anchor":"forked-background-sessions-get-an-explicit-worktree-warning","heading":"Forked background sessions get an explicit worktree warning injected into transcript","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/forked-background-sessions-get-an-explicit-worktree-warning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Forked background sessions get an explicit worktree warning injected into transcript\n\nA forked background session now gets a transcript message warning it never to edit the parent worktree.\n\nWhen spawning a background or forked session with `keepParent`, a synthetic \"fork_briefing\" message is now inserted directly into the new session's transcript, not just the system prompt. It warns the forked session never to edit files in the original session's worktree and to create its own instead, referencing the parent's `worktreePath` and `worktreeBranch`.\n\n- Area: Sessions\n- Names: `keepParent`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}