Event uploads can be held while a session has no subscribers, but the hold duration comes from a remote flag defaulting to zero.
The CCRClient's durable and internal event uploaders can now hold event uploads when a session has no subscribers. A new noSubscriberUploadHoldMs setting, set via setNoSubscriberUploadHoldMs, works with a holdMaxItems: 50 cap on the internal-event uploader; releasing a hold logs telemetry event ccr_no_subscriber_hold with lane, reason, held_events, and held_ms. The hold duration comes from remote flag tengu_ccr_no_subscriber_hold_ms and defaults to 0 (also forced to 0 for outbound-only sessions), so the hold is inactive unless the server pushes a positive value.
tengu_ccr_no_subscriber_hold_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.259: no gate table built for this version
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.259. 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_no_subscriber_hold_ms