{"version":"2.1.290","anchor":"debug-log-rate-limits-and-sse-stream-body-cap","canonical_anchor":"debug-log-rate-limits-and-sse-stream-body-cap","heading":"Debug logs and streamed responses now have size limits","tier":"notice","area":"Streaming","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/debug-log-rate-limits-and-sse-stream-body-cap","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Debug logs and streamed responses now have size limits\n\nDebug log messages are now capped in length and rate, and streamed server responses are capped in total size\n\n**Unclear.** The exact limit values are not known.\n\n**What**\n\nClaude Code now puts limits on two things:\n\n- Debug logs: each message has a maximum length, and only so many messages are let in. When messages are dropped, the log says how many were not logged.\n\n- Streamed responses: data Claude Code receives as a stream from a server now has a cap on its total size. While handling it, Claude Code also pauses every 8 milliseconds to let other work run.\n\n**Why**\n\nThese limits stop a flood of log messages or streamed data from overwhelming Claude Code.\n\n- Area: Streaming\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}