{"version":"2.1.314","anchor":"ccr-client-tool-input-stream-deltas-throttled-metadata-flu","canonical_anchor":"ccr-client-tool-input-stream-deltas-throttled-metadata-flu","heading":"Remote session uploader: slower tool-input flushing, metadata saved at shutdown","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/ccr-client-tool-input-stream-deltas-throttled-metadata-flu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Remote session uploader: slower tool-input flushing, metadata saved at shutdown\n\nThe remote-session client now batches large tool-input updates on a slower timer, flushes owed metadata on exit, and tracks a few more internal states\n\n**What**\n\nThis applies to remote sessions, where Claude Code runs on a remote worker and streams its progress back. The part of Claude Code that sends updates from that worker, called the CCR client, changed in several ways:\n\n- Large tool inputs: when Claude prepares the input for a tool (an action such as editing a file or running a command), that input arrives in small pieces called `input_json` deltas. Updates for large ones are now sent on a slower timer, controlled by `toolInputFlushMs` and set through a new `setToolInputFlushMs` setting. A new `ccr_tool_input_flush` event is logged. Before, all stream updates used one shared interval.\n\n- Shutdown: when the session ends, any worker metadata still waiting to be sent is now flushed. The result is logged as `cli_worker_metadata_at_shutdown`, with an outcome of `drained`, `timed_out`, `cut` or `refused`. Before, shutdown flushed only internal events and client events.\n\n- Live rows: live updates are now stamped with `live_turn_id`, `live_index` and `emitted_at_ms`.\n\n- Status markers: the client adds `ridesAStatus: [\"reply_degraded\", \"card_turn_stamp\"]`.\n\n- Housekeeping requests: housekeeping control requests are now marked so their ids are tracked.\n\n- Dropped batches: `lastTaskList` is cleared when batches of durable events are dropped.\n\n**Why**\n\nThese are mostly behind-the-scenes changes to remote sessions. In practice, large tool inputs should cause fewer separate uploads, and session metadata that has not been sent yet is no longer simply abandoned when the session exits.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}