{"version":"2.1.227","anchor":"forks-keep-the-parent-s-suppressed-history","canonical_anchor":"forks-keep-the-parent-s-suppressed-history","heading":"Forks keep the parent's suppressed history","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/forks-keep-the-parent-s-suppressed-history","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Forks keep the parent's suppressed history\n\nForking a session with suppressed history keeps that suppression instead of restoring it.\n\n**What**\n\nWhen a session's transcript history was suppressed, forking it now records that suppression on the fork with reason \"fork_inherit\" rather than starting the fork with clean history.\n\n**Details**\n\n- a `precautionarySuppressionHeld` flag is carried across resume and fork so a held suppression is re-applied under the new session id\n\n**Evidence**\n\n`fork_inherit`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}