{"version":"2.1.275","anchor":"tool-result-binary-content-hook-output-persistence-now-f","canonical_anchor":"tool-result-binary-content-hook-output-persistence-now-f","heading":"Tool result \/ binary content \/ hook output persistence now falls back to an in-transcript truncation preview when disk save is unavailable","tier":"notice","area":"Tool Results","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/tool-result-binary-content-hook-output-persistence-now-f","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Tool result \/ binary content \/ hook output persistence now falls back to an in-transcript truncation preview when disk save is unavailable\n\nLarge tool outputs that can't be saved to disk now show a truncated preview instead of being silently cut or dropped\n\n**What**\n\nLarge tool results, hook outputs (output from custom scripts that run at certain points), and binary content are normally saved to disk when they're too big to keep in the conversation directly. When disk storage isn't available to save them, Claude Code now builds a truncated preview shown inline in the conversation, marked with an explicit `<truncated-output>` label and a message explaining that the output was too large, couldn't be saved, and only the first part is shown.\n\n**Why**\n\nThis makes it clear when output has been cut short because it couldn't be saved, rather than leaving the loss silent or unexplained.\n\n- Area: Tool Results\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}