{"version":"2.1.281","anchor":"session-resume-respawn-plumbing","canonical_anchor":"session-resume-respawn-plumbing","heading":"Session resume \/ respawn plumbing","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/session-resume-respawn-plumbing","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Session resume \/ respawn plumbing\n\nInternal replies used when starting, moving or resuming a session gain new fields such as `freshSession` and `reattachEnvDropped`\n\n**Unclear.** The finding does not say what the `leafUuid` filter checks or whether any of the new fields change what a reader sees.\n\n**What**\n\nA session is one continuous conversation with Claude Code. Several internal replies that Claude Code uses when it starts, moves or resumes a session now carry extra fields:\n\n- `freshSession` in the reply to a change of working folder (`set_cwd`)\n\n- `reattachEnvDropped` in the result of starting a new session\n\n- `sessionRoot` in results that report the root folder of a git repository\n\nThe saved marker for where a resumed session picks up (`leafUuid`) is now set to the last message that fails a filter. Before, it pointed at a fixed message.\n\n**Why**\n\nThese are behind-the-scenes changes. The one most likely to matter in practice is the `leafUuid` change, because it decides which message a resumed session treats as its latest."}