{"version":"2.1.315","anchor":"resume-only-keeps-the-cut-off-tool-call-if-it-belongs-to-the","canonical_anchor":"resume-only-keeps-the-cut-off-tool-call-if-it-belongs-to-the","heading":"Resuming a copied session no longer shows a stray cut-off tool call","tier":"notice","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/resume-only-keeps-the-cut-off-tool-call-if-it-belongs-to-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### Resuming a copied session no longer shows a stray cut-off tool call\n\nResume now keeps an interrupted tool call only if it belongs to the session that was copied\n\n**What**\n\nA tool call is a single action Claude takes, such as running a command. When you resume a session that stopped mid-action, Claude Code used to always keep that cut-off call. If the session is a copy of another one, it now keeps the call only when it belongs to the copied session, and drops it otherwise.\n\n**Why**\n\nResuming a forked or copied session no longer shows an interrupted call that came from somewhere else.\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}