{"version":"2.1.223","anchor":"cloud-stream-event-flush-interval-is-now-remote-configurable","canonical_anchor":"cloud-stream-event-flush-interval-is-now-remote-configurable","heading":"Cloud stream-event flush interval is now remote-configurable","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223\/e\/cloud-stream-event-flush-interval-is-now-remote-configurable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.223","markdown":"### Cloud stream-event flush interval is now remote-configurable\n\nHow often cloud session events are batched can now be tuned remotely instead of being fixed.\n\n**What**\n\nThe CCR client's stream-event batching interval moved from a fixed constant to an option read from a gate, so it can be tuned without a release.\n\n**Details**\n\n- Read from `tengu_ccr_stream_event_flush_ms`, whose fallback is the old 100 ms constant.\n- Clamped to the range 0 to 60000 ms.\n- A non-finite value logs a warning and falls back to the default.\n- Plumbed through the remote-bridge transport setup and the reconnect paths.\n\n**Evidence**\n\n`tengu_ccr_stream_event_flush_ms`\n\n- Flag `tengu_ccr_stream_event_flush_ms`: Not enough to say (read for one account on one subscription tier against v2.1.223; this account: no value returned, anonymous baseline: no value returned, compiled default: not a boolean we can read) These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}