tengu_ccr_no_subscriber_hold_ms

A Claude Code feature flag, read out of the shipped bundle. It has been in the build since v2.1.259, including the newest one read.

Releases whose published page names tengu_ccr_no_subscriber_hold_ms.

1. v2.1.259 2 Sep 2026
   Two new CCR (remote-control) heartbeat/upload tuning gates

   Remote-control worker connections gained tuning gates for an upload hold delay and for skipping redundant heartbeats.

   found in this entry's text, named in this entry, gate cited by this entry

2. v2.1.259 2 Sep 2026
   CCR client can hold event uploads while no one is subscribed

   Event uploads can be held while a session has no subscribers, but the hold duration comes from a remote flag defaulting to zero.

   found in this entry's text, named in this entry, gate cited by this entry

3. v2.1.259 2 Sep 2026
   Bridge teardown can hold for pending uploads before closing transport

   Remote bridge teardown can hold briefly to flush pending uploads before closing the transport, with the hold time recorded.

   gate cited by this entry

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.

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.

The earliest release whose published evidence quoted tengu_ccr_no_subscriber_hold_ms was v2.1.259, 2 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.

One 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.