Remote Control sessions can now delay and tune how the very first streamed event is sent to the backend
What
The client that uploads events for Remote Control (bridge) sessions gained a new streamEventFirstFlushMs setting, alongside an existing setStreamEventFlushIntervalMs setter:
- When
streamEventFirstFlushMsis set to a value greater than zero, the very firststream_eventis buffered as ephemeral instead of being sent immediately, short-circuiting the normal flush-interval batching just for that first event. - Both the flush interval and this new first-flush delay are now pushed into the client at runtime via the periodic config-apply routine, alongside the existing no-subscriber flush interval, no-subscriber upload hold, and drop-unwatched-events settings.
- The setting defaults to 0 (no delay) and is read from remote config.
Why
This gives finer control over how quickly the first event of a Remote Control session reaches the backend, which can be tuned separately from the steady-state flush interval used for events after a subscriber is actively watching.
tengu_ccr_stream_first_flush_ms Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.273: 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.
Read once, for one account on one subscription tier, against v2.1.273. It isn't a statement about your account. What a flag value here can and cannot tell you
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
A reading is one sample. Claude Code evaluates its flags remotely, so no client sees the targeting rule behind a value and this says nothing about your account.
Whether `tengu_ccr_stream_first_flush_ms` is enabled for any account is unread, so nothing can be said about whether this behavior is…
New in this build: tengu_ccr_stream_first_flush_ms