Follow Discord
Sweep 22 Sep 2026 · 17:19Z Build v2.1.280 501 read Stable v2.1.267 Latest v2.1.280 Next v2.1.280 Feeds RSS JSON llms.txt Unofficial
Claude Code v2.1.268 ·

New CCR flags for event holding and dropping unwatched stream events

Two new remote flags let the CCR client hold served-policy events and drop stream events nobody is watching

TierNothing to try yethow much it should matter to you
Useful2my rating, 1 to 5
Signal2worth watching, 1 to 5
AreaTelemetrywhat it touches
KindIn Developmentin v2.1.268,
Group of 3 Nothing to try yet

Two new remote flags let the CCR client hold served-policy events and drop stream events nobody is watching

What

  • A new eventHoldEnabled flag (on by default) enables holding of served-policy events, and a new dropUnwatchedStreamEvents flag (off by default) drops stream events entirely when no subscriber is watching them. Both are wired into the CCR (client-cloud relay) worker config.
  • The CCR client now passes dropUnwatchedStreamEvents at construction, and this can be toggled live via a GrowthBook-refresh subscription that calls setDropUnwatchedStreamEvents.
  • The CCR client also gains an eventHoldEnabled callback option, backed by a GrowthBook flag.

Why These flags give more control over event traffic in remote/CCR sessions, reducing unnecessary event delivery when nothing is subscribed and allowing event-holding behavior to be toggled remotely without a client update.

Read from
Feature flag
tengu_ccr_event_hold_enabled Not enough to say

Nothing 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.268: on

tengu_ccr_drop_unwatched_stream_events Not enough to say

Nothing 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.268: off

Read once, for one account on one subscription tier, against v2.1.268. It isn't a statement about your account. What a flag value here can and cannot tell you

What has happened since
Flag reading moved The flag server now returns on for tengu_ccr_drop_unwatched_stream_events, read as this 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.
Flag reading moved The flag server now returns off for tengu_ccr_drop_unwatched_stream_events, read as this 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.
Flag reading moved The flag server now returns on for tengu_ccr_drop_unwatched_stream_events, read as this 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.

See this across every release →

How sure we are
One source agreesOne thing we can check says the same as this entry.
The name it cites is new in this buildNew in this build: tengu_ccr_drop_unwatched_stream_events

See this entry in the whole of v2.1.268 →

Feedback