{"version":"2.1.319","anchor":"output-truncation-errors-now-flagged-as-cut-in-an-unfinished","canonical_anchor":"output-truncation-errors-now-flagged-as-cut-in-an-unfinished","heading":"Responses cut off by the output limit are now marked as cut mid-block","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/output-truncation-errors-now-flagged-as-cut-in-an-unfinished","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Responses cut off by the output limit are now marked as cut mid-block\n\nWhen a reply hits the maximum output length, its error now carries cutInUnfinishedBlock: true to show it stopped partway through a block\n\n**Unclear.** What Claude Code does differently with a reply marked this way is not known.\n\n**What**\n\nClaude's replies have a maximum length. When a reply hits it, Claude Code builds an error message. That message now also carries `cutInUnfinishedBlock: true`, meaning the reply stopped partway through a block of content. Before, it carried only the content and the error details.\n\n**Why**\n\nOther parts of Claude Code can now handle a reply cut off in the middle of a block differently from other cut-off replies.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}