Group of 2 Under the hood
No documentation found
Headless and print-resume sessions now track a fork_seed_sha256 seed to adopt prior transcript rows when forking from a remote-controlled session
What
Claude Code's remote-control fork handling now uses a seed value, fork_seed_sha256, to connect a forked session back to rows from its parent.
- In headless mode (
-p), when given an sdkUrl and credentials, Claude Code writesfork_seed_sha256into the session's internal metadata and threads aremoteControlForkChildvalue through the streaming loop. - In the
--print --resumepath, Claude Code now asksremoteControlForkChild.adoptSeed(...)to look up rows matching thatfork_seed_sha256, feeds the resulting rows in asprecedingRowsduring session loading, and filters out any rows already adopted from what gets shown in the transcript (tracked via aliveSourceRowsset). A new normalization pass runs over the loaded session data before existing checks.
Why
This lets a forked or resumed session correctly pick up conversation history from a remote-controlled parent session instead of starting without that context or duplicating rows.
Names in the bundlefork_seed_sha256
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding shows the metadata field being written but not what consumes fork_seed_sha256 or remoteControlForkChild or why.