{"version":"2.1.268","anchor":"rewind-conversation-and-the-new-fork-conversation-share-a-co","canonical_anchor":"rewind-conversation-and-the-new-fork-conversation-share-a-co","heading":"rewind_conversation and the new fork_conversation share a common target-lookup and blocked-state helper","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/rewind-conversation-and-the-new-fork-conversation-share-a-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### rewind_conversation and the new fork_conversation share a common target-lookup and blocked-state helper\n\nrewind_conversation and the new fork_conversation now share the same logic for finding a target message and checking if the session is busy\n\n**What**\n\nThe handling code for `rewind_conversation` and the newer `fork_conversation` control requests now shares a common function for looking up the target message and a common check for whether the session is busy or blocked. This replaces `rewind_conversation`'s previous, more elaborate custom logic for searching through stacked expansions and queued commands to find its target.\n\n**Why**\n\nThis is a code consolidation that makes the two related features behave consistently, rather than a new capability for the reader.\n\n- Area: Sessions\n- Names: `rewind_conversation`, `fork_conversation`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}