{"version":"2.1.273","anchor":"background-spawn-fork-now-supports-resuming-at-a-specific","canonical_anchor":"background-spawn-fork-now-supports-resuming-at-a-specific","heading":"Background spawn \/ fork now supports resuming at a specific leaf message","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/background-spawn-fork-now-supports-resuming-at-a-specific","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Background spawn \/ fork now supports resuming at a specific leaf message\n\nForking a background session can now resume at a specific earlier message\n\n**What**\n\nThe internal function used to spawn a background agent or fork a conversation now accepts a `resumeAtLeaf` option, letting it resume from a specific message rather than the latest one. If the conversation no longer actually contains that message as a valid fork point, it now returns a clear error: \"Couldn't fork - the conversation no longer contains the fork point,\" instead of proceeding incorrectly.\n\n**Why**\n\nThis lets background forks branch from a precise earlier point in a conversation, and fails clearly and safely if that point has since disappeared (for example, after history was pruned).\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}