{"version":"2.1.280","anchor":"tool-output-truncation-now-appends-an-explanatory-note","canonical_anchor":"tool-output-truncation-now-appends-an-explanatory-note","heading":"Tool output truncation now appends an explanatory note","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/tool-output-truncation-now-appends-an-explanatory-note","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Tool output truncation now appends an explanatory note\n\nTruncated tool output can now include an explanatory note about why it was cut short\n\n**Unclear.** The finding does not say which tools supply a truncationNote or what the note's wording looks like in practice.\n\n**What**\n\nWhen a tool's output is too long and gets cut short (truncated), Claude Code can now attach a `truncationNote`: a short explanatory message added after the shortened content, separated from it by a blank line. The note only appears when truncation actually happened and a note was provided.\n\n**Why**\n\nThis gives a clearer signal when output has been shortened, instead of leaving the reader to guess why the content stops abruptly or seems incomplete.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}