{"version":"2.1.273","anchor":"new-fork-failure-notice-posted-into-the-forked-session","canonical_anchor":"remote-control-conversation-fork-fork-conversation-wired-i","heading":"Remote Control can fork a running conversation","tier":"notice","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/new-fork-failure-notice-posted-into-the-forked-session","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Remote Control can fork a running conversation\n\nA remote client can now ask Claude Code to fork the current conversation into a new branch, with a notice posted if it fails\n\n**What**\n\n- A new `fork_conversation` bridge control request is now wired into the REPL for Remote Control sessions. It validates a target message UUID and title, then spawns a background fork of the current conversation, letting a remote client branch a running session mid-conversation.\n\n- If starting that fork fails, Claude Code now posts an informational\/warning message into the newly forked session explaining that the fork could not be started.\n\n**Why**\n\nThis lets remote clients branch an in-progress conversation without losing context, and makes sure the user still finds out if the fork didn't actually start.\n\n- Area: Remote Control\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 3\/5"}