{"version":"2.1.321","anchor":"stream-delta-events-batched-in-the-bufferephemeral-path","canonical_anchor":"stream-delta-events-batched-in-the-bufferephemeral-path","heading":"Streamed text is batched more directly when Claude Code sends it to another program","tier":"internal","area":"Streaming","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/stream-delta-events-batched-in-the-bufferephemeral-path","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Streamed text is batched more directly when Claude Code sends it to another program\n\nPieces of streamed output now go straight into the waiting batch when a send timer is already running, and tool input is counted per tool call\n\n**What**\n\nWhen Claude Code passes its output to another program as it is written, it collects small pieces into batches and sends them on a timer. If a timer is already running and Claude Code is not in slow mode, each new piece of streamed content now goes straight into the batch, skipping the check it used to make for every piece.\n\nClaude Code also now counts how many characters of input are streamed for each tool call (each time Claude uses one of its tools).\n\n**Why**\n\nThis is a faster path for streaming. It may change how output arrives in batches for remote sessions or for programs that drive Claude Code.\n\n- Area: Streaming\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}