Resumed sessions keep rewind points, where they came from, and denied tools

What

A session is one conversation with Claude Code, and resuming picks it up again later. Resuming now carries more of the session's history with it.

• Rewind cut: a rewindCut is read from the transcript (the saved record of the session) and passed through the result of --resume in print mode, the non-interactive mode used by scripts and the SDK. A new mirrorRewindMarker writes the rewind marker to the cloud session's event stream.
• Where a session came from: transcripts now hold derived-from entries, each a session ID with a via of branch, background, fork, resume or compact, plus data-flow records. They are restored when a session loads. Compaction, which shortens a long conversation, records via: "compact", and CLAUDE_CODE_RESUME_SOURCE_ALIVE selects background. Before, only tool-use and connector data flags were recorded on resume.
• Copied sessions: print-mode resume records parent sessions and marks a copied session as incomplete. When CLAUDE_CODE_RESUME_FROM_SESSION fills in the session, that source is recorded.
• Denied tools: tools disallowed for a turn and for the client are saved as turn_deny_lists in the remote worker's internal data. After a restart, if those lists cannot be read, Claude Code does not resume the interrupted turn or the cut-off agent. This applies only when CLAUDE_CODE_RESUME_INTERRUPTED_TURN is set on a remote connection.
• Teleport failures: in print mode these now print the error in the chosen output format and stop. Before, they logged "Teleport in print mode failed:" and carried on with no messages.
• Load time: how much processing time loading a resumed session took is now recorded.
• Last-prompt entries only set explicit when asked to.

Why

Resumed, forked and background sessions behave more consistently after a rewind or compaction, and keep track of which session they came from. A tool you denied for a turn does not become usable again just because a remote worker restarted.