tengu_expressive_whistle compiles in false, so the throttled refetch path never runs.
When the server signals that Claude Code's cached client data is out of date, the refetch is rate-limited. Those limits moved from fixed values to a server-supplied config, tengu_expressive_whistle_config: a minimum interval defaulting to 300 seconds (clamped 30 to 86400) and jitter defaulting to 180 seconds (clamped 0 to 3600). The whole path sits behind tengu_expressive_whistle, whose compiled fallback is false, so without a server value it never runs.
- Both resolved values are reported in the refetch event as
min_interval_msandjitter_ms. - The config key defaults to an empty object, so the defaults above apply if the gate is turned on without config.
tengu_expressive_whistle_config
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
tengu_expressive_whistle Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.248: off
Read once, for one account on one subscription tier, against v2.1.248. 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.
New in this build: tengu_expressive_whistle_config