{"version":"2.1.318","anchor":"main-reply-stream-hold-telemetry-and-a-hold-release-rule","canonical_anchor":"main-reply-stream-hold-telemetry-and-a-hold-release-rule","heading":"Streamed main replies are held back and released by a separate rule","tier":"internal","area":"Streaming","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/main-reply-stream-hold-telemetry-and-a-hold-release-rule","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Streamed main replies are held back and released by a separate rule\n\nClaude Code now tracks held-back main replies separately while streaming, and releases one early when a block starts arriving\n\n**Unclear.** It is not clear whether the separate main-reply handling is ever active, so the visible effect is unknown.\n\n**What**\n\nWhile a reply streams in, Claude Code can briefly hold back the output before showing it. It used to track this with a single flag shared by all replies. It now tracks the main reply separately and reports holds on it as a separate kind of event.\n\nIt also releases a held reply early when the first piece of a content block arrives before any complete block has come in.\n\n**Why**\n\nThis could change how and when streamed output appears on your screen.\n\n- Area: Streaming\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}