{"version":"2.1.321","anchor":"streaming-watchdog-held-streams-and-new-viewer-hold","canonical_anchor":"streaming-watchdog-held-streams-and-new-viewer-hold","heading":"Internal changes to how streamed replies are held and how redirects are followed","tier":"internal","area":"Network","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/streaming-watchdog-held-streams-and-new-viewer-hold","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Internal changes to how streamed replies are held and how redirects are followed\n\nClaude Code now tells its main reply stream from other streams, can stop holding back parts of a stream, and follows redirects on retries\n\n**What**\n\nClaude Code receives replies as a stream, piece by piece. It now marks each stream as the main reply or something else, can be told to stop holding back pieces, and counts the pieces it held. When a request is retried, it tracks the address for each attempt, so a request that was redirected to a new address is handled.\n\n**Why**\n\nThis is internal plumbing for streaming and display, with little you would notice directly.\n\n- Area: Network\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}