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 bundle--print --resumefork_seed_sha256
--print
CLI reference modified, high confidence
| `--bg`, `--background` | Start the session as a [background agent](/docs/en/agent-view) and return immediately. Prints the session ID and management commands. Combine with `--exec` to run a shell command as a background job instead of a …see the edit
--print
Claude Code changelog modified, high confidence
* Fixed PermissionRequest hooks not firing in `--print` modesee the edit
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Added since
A small documentation edit on CLI reference touched a line naming --print after this was published.
| `--bg`, `--background` | Start the session as a [background agent](/docs/en/agent-view) and return immediately. Prints the session ID and management commands. Combine with `--exec` to run a shell command as a background job instead of a …cli-reference see the edit
Confirmed since
Anthropic's documentation has since written up --print, on Error reference.
| `--bg and --print conflict` | [Command-line errors](#command-line-errors) |errors see the edit
Two sources agreeTwo things we can check say the same as this entry.
Anthropic's documentation agrees
--print on CLI reference
Anthropic's release notes agree
Fixed PermissionRequest hooks not firing in --print mode