{"version":"2.1.268","anchor":"print-mode-resume-gains-cloud-session-fork-seed-adoption-and","canonical_anchor":"headless-remote-control-fork-now-tracks-a-fork-seed-sha256","heading":"Remote-control session forking gains a seed-based resume mechanism","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/print-mode-resume-gains-cloud-session-fork-seed-adoption-and","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Remote-control session forking gains a seed-based resume mechanism\n\nHeadless and print-resume sessions now track a fork_seed_sha256 seed to adopt prior transcript rows when forking from a remote-controlled session\n\n**What**\n\nClaude 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.\n\n- In headless mode (`-p`), when given an sdkUrl and credentials, Claude Code writes `fork_seed_sha256` into the session's internal metadata and threads a `remoteControlForkChild` value through the streaming loop.\n\n- In the `--print --resume` path, Claude Code now asks `remoteControlForkChild.adoptSeed(...)` to look up rows matching that `fork_seed_sha256`, feeds the resulting rows in as `precedingRows` during session loading, and filters out any rows already adopted from what gets shown in the transcript (tracked via a `liveSourceRows` set). A new normalization pass runs over the loaded session data before existing checks.\n\n**Why**\n\nThis 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.\n\n- Area: Sessions\n- Names: `--print --resume`, `fork_seed_sha256`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}