{"version":"2.1.246","anchor":"tool-renderers-can-tell-an-interrupted-call-from-a-failed-on","canonical_anchor":"tool-renderers-can-tell-an-interrupted-call-from-a-failed-on","heading":"Tool renderers can tell an interrupted call from a failed one","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/tool-renderers-can-tell-an-interrupted-call-from-a-failed-on","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Tool renderers can tell an interrupted call from a failed one\n\nA tool call you interrupted now displays differently from one that actually failed.\n\n**What**\n\nThe data passed to a tool's display code now includes an `interrupted` flag taken from the tool result, so a call you cut off renders differently from one that errored. The system-message renderer also gained a branch for the new cloud session status notice.\n\n**Details**\n\n- The flag is derived from the tool result rather than from UI state, so it applies to custom tool renderers as well as built-in ones.\n- No flag guards either addition in the code around them.\n\n**Evidence**\n\n`cloud_session_status`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}