A remote client can now ask Claude Code to fork the current conversation into a new branch, with a notice posted if it fails
What
- A new
fork_conversationbridge 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. - 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.
Why
This 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.
tengu_cozy_pixel Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.273: off
These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.
Read once, for one account on one subscription tier, against v2.1.273. It isn't a statement about your account. What a flag value here can and cannot tell you