{"version":"2.1.274","anchor":"fork-conversation-now-rejects-targets-that-split-a-tool-call","canonical_anchor":"fork-conversation-now-rejects-targets-that-split-a-tool-call","heading":"Fork-conversation now rejects targets that split a tool call","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/fork-conversation-now-rejects-targets-that-split-a-tool-call","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Fork-conversation now rejects targets that split a tool call\n\nForking a conversation now refuses fork points that would split a tool call from its result\n\n**What**\n\nWhen forking a conversation at a specific message, Claude Code now checks whether that fork point would separate a tool call (`tool_use`) from its result (`tool_result`). If it would, the fork is refused with an error instead of proceeding.\n\n**Why**\n\nThis prevents creating a forked conversation whose transcript would be invalid because a tool call is missing its matching result.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}