{"version":"2.1.323","anchor":"resume-path-adds-repl-session-rewind-handling-and-in-process","canonical_anchor":"resume-path-adds-repl-session-rewind-handling-and-in-process","heading":"Resuming a conversation restores more of its interactive code session state","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/resume-path-adds-repl-session-rewind-handling-and-in-process","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Resuming a conversation restores more of its interactive code session state\n\nOn resume, Claude Code now restores state for interactive code sessions tied to tool calls in the restored conversation\n\n**Unclear.** It is not clear what you would see differently after resuming.\n\n**What**\n\nWhen you resume a conversation, Claude Code now restores rewound state for its interactive code sessions (REPL sessions). It uses the tool calls found in the restored conversation to do this. A tool call is a single action Claude takes, such as running code. The cleanup at the end of the main conversation now runs only when the resumed session is a different one, and Claude Code also notes when a resume happens inside the same running process.\n\n**Why**\n\nThis changes what interactive code session state comes back after a resume.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}