{"version":"2.1.273","anchor":"repl-bridge-child-auto-revivereconnect-flow-renamedreworke","canonical_anchor":"repl-bridge-child-auto-revivereconnect-flow-renamedreworke","heading":"REPL bridge child auto-revive\/reconnect flow renamed\/reworked; new onForkConversation control op","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/repl-bridge-child-auto-revivereconnect-flow-renamedreworke","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### REPL bridge child auto-revive\/reconnect flow renamed\/reworked; new onForkConversation control op\n\nRemote-control bridge session gains an onForkConversation control op, plus a reworked reconnect flow\n\n**What**\n\nThe code handling the remote-control mirror session (the \"bridge\" that lets a remote session shadow a local one) was substantially reshuffled internally, mostly renaming variables from a rebuild. It also gained a new `onForkConversation` control operation: a remote bridge session can now request forking the conversation, using a snapshot of the messages, the current turn-activity state, and the length of any queued commands, and the resulting child bridge session is then recorded.\n\n**Why**\n\nThis lets a remote-control session trigger a conversation fork remotely, extending what remote sessions can do to a locally-running Claude Code session.\n\n- Area: Remote Control\n- Names: `onForkConversation`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}