{"version":"2.1.288","anchor":"http-body-overflow-error-message-reworded","canonical_anchor":"http-body-overflow-error-message-reworded","heading":"Clearer error when a server sends back too much data","tier":"notice","area":"Internals","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288\/e\/http-body-overflow-error-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.288","markdown":"### Clearer error when a server sends back too much data\n\nThe error for an oversized server response now says the server streamed more than a set number of MB, so the response was not read\n\n**What**\n\nWhen a server keeps sending data past the size limit Claude Code allows, Claude Code stops reading and shows an error. That error now says the server streamed more than a given number of megabytes, so the response was not read.\n\nThe old message said the server was likely returning non-protocol data and that Claude Code was disconnecting to prevent unbounded memory growth.\n\n**Why**\n\nYou see this message directly, and the new wording says plainly what happened: the response was too big and was not read.\n\n- Area: Internals\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}