Under the hood
No documentation found
Remote-control bridge session gains an onForkConversation control op, plus a reworked reconnect flow
What
The 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.
Why
This lets a remote-control session trigger a conversation fork remotely, extending what remote sessions can do to a locally-running Claude Code session.
Names in the bundleonForkConversation