{"version":"2.1.284","anchor":"streamed-content-block-start-with-no-content-block-now-fails","canonical_anchor":"streamed-content-block-start-with-no-content-block-now-fails","heading":"Malformed streamed replies now fail with \"Stream event unreadable\"","tier":"notice","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/streamed-content-block-start-with-no-content-block-now-fails","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### Malformed streamed replies now fail with \"Stream event unreadable\"\n\nA broken piece of a streamed reply now stops with the error \"Stream event unreadable\" instead of carrying on with bad data\n\n**Unclear.** Whether Claude Code retries the request after this error is not clear.\n\n**What**\n\nClaude's replies arrive as a stream of small pieces. If one piece announces the start of a new block of content but contains no actual content, Claude Code now stops with the error \"Stream event unreadable\" and records the problem. Before, it carried on with the broken block.\n\n**Why**\n\nIf a proxy or gateway between you and the API corrupts a reply, you should get a clear error rather than a confusing crash later.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}