{"version":"2.1.227","anchor":"forking-a-session-from-the-resume-picker-now-carries-history","canonical_anchor":"forking-a-session-from-the-resume-picker-now-carries-history","heading":"Forking a session from the resume picker now carries history suppression forward","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/forking-a-session-from-the-resume-picker-now-carries-history","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Forking a session from the resume picker now carries history suppression forward\n\nForking a session from the resume picker now carries over suppression and parent records properly.\n\n**What**\n\nForking a past session from the resume picker previously only replayed content replacements. It now runs the shared fork helper, which strips the source session's worktree session and relocated working directory, records the fork's parent, and copies history suppression onto the new session id when the source was suppressed or known to be tainted.\n\n**Details**\n\n- The suppression record on the destination session is written with cause `fork_inherit`.\n- The fork helper is called with `stripWorktreeSession` and `stripRelocatedCwd` set, plus the destination session id.\n- Neither the suppression record type nor the fork options existed in v2.1.226, so forks made from this path previously started without inherited suppression.\n\n**Evidence**\n\n`stripWorktreeSession`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}