tengu_ccr_stream_first_flush_ms
A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.273, including the newest one read.
CCR client can now delay the very first streamed event separately from later ones, via a new first-flush timing setting
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.273.
In the changelogs
2Releases whose published page names tengu_ccr_stream_first_flush_ms.
-
v2.1.273
CCR client gains a 'first flush' delay for streamed events
CCR client can now delay the very first streamed event separately from later ones, via a new first-flush timing setting
gate cited by this entry
-
v2.1.273
New gate for delaying the first CCR stream-event flush
A new setting can make the first telemetry stream event flush immediately instead of waiting for the normal batching interval
gate cited by this entry
Gate readings
1| Release | Resolved | This account | Anonymous | Compiled default |
|---|---|---|---|---|
| v2.1.273 read on another version | Not enough to say | no value returned | no value returned | not a boolean we can read |
Two arms, because they disagree: this account is the one account this site reads and anonymous is a baseline with no identity attached. A reading says nothing about your account, and off cannot rule out a rollout both readings sit outside of. What these readings can and cannot show.
Flag server, over time
8| Read as | Reading | From | Until | Version installed |
|---|---|---|---|---|
| this account | 20 | 2026-09-18T19:25:05Z | 2026-09-29T21:15:05Z | v2.1.277 to v2.1.285 |
| anonymous | 20 | 2026-09-18T19:05:04Z | 2026-09-29T21:15:05Z | v2.1.277 to v2.1.285 |
| this account | 100 | 2026-09-18T17:20:05Z | 2026-09-18T19:05:04Z | v2.1.276 to v2.1.277 |
| anonymous | 100 | 2026-09-17T22:10:04Z | 2026-09-18T19:00:07Z | v2.1.274 to v2.1.277 |
| this account | 20 | 2026-09-18T17:16:15Z | 2026-09-18T17:16:15Z | v2.1.277 |
| this account | 100 | 2026-09-17T22:30:05Z | 2026-09-18T16:20:04Z | v2.1.274 to v2.1.276 |
| this account | null | 2026-09-14T21:40:04Z | 2026-09-17T22:10:04Z | v2.1.270 to v2.1.274 |
| anonymous | null | 2026-09-14T21:10:04Z | 2026-09-17T21:45:04Z | v2.1.270 to v2.1.274 |
One row per unbroken stretch of one reading, newest first, from snapshots taken every twenty-five minutes or so. No longer carried is not off: it means the flag server stopped returning the gate at all, which is what a retired experiment looks like. The version column is what was installed when the reading was taken, not what caused it.
First cited
1The earliest release whose published evidence quoted tengu_ccr_stream_first_flush_ms was v2.1.273, 15 Sep 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
1Build by build
12One row per release since the first build this name was read out of. Absent means the build was read and the name was not in it, never mined means no bundle for that release was ever archived, and a declared type or a default is only ever what that release's own bundle stated.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the feature flag does. All feature flags.