The 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.
- Read from
tengu_ccr_stream_event_flush_ms, whose fallback is the old 100 ms constant. - Clamped to the range 0 to 60000 ms.
- A non-finite value logs a warning and falls back to the default.
- Plumbed through the remote-bridge transport setup and the reconnect paths.
tengu_ccr_stream_event_flush_ms
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_ccr_stream_event_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.223: 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.223. 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.
New in this build: tengu_ccr_stream_event_flush_ms