{"version":"2.1.314","anchor":"stream-event-hold-in-the-remote-transport-plus-a-tool-input","canonical_anchor":"stream-event-hold-in-the-remote-transport-plus-a-tool-input","heading":"Remote sessions can hold back streamed output, with a new tool-input flush setting","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/stream-event-hold-in-the-remote-transport-plus-a-tool-input","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote sessions can hold back streamed output, with a new tool-input flush setting\n\nRemote sessions can hold streamed output until there is activity, and gain a setting for how often tool input is sent on\n\n**What**\n\nIn a remote session, Claude Code streams its output piece by piece to whoever is watching. That stream can now be held back. While it is held, pieces are dropped. The hold ends when there is new activity or a held write comes through, and it stops if the input fails badly.\n\nThe remote client also has a new setting, `setToolInputFlushMs`, for how often the input being built for a tool is sent on. It joins the existing settings for flushing streamed events. Claude Code also reports timing details about the first reply, such as how long output was held and how many pieces were read.\n\n**Why**\n\nThis changes how and when streamed output reaches someone watching a remote session, and adds reporting about it.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}