Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.308 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.0.54 ·

Telemetry Event Sampling

Entry
JSON All of v2.0.54
EntryKind: in v2.0.54,
ChangesSection of the release

What: Probabilistic sampling mechanism that reduces telemetry overhead by logging only a configurable fraction of events.

Details:

  • Sampling rates configured via Statsig dynamic config tengu_event_sampling_config
  • Per-event sample rates between 0 and 1 (0% to 100%)
  • When sampled, events include sample_rate metadata for statistical reconstruction
  • Events with sample_rate: 0 are completely dropped
  • Evidence: lg1() at line 231903, ZD6() at line 231900, modified ZA() at line 507257
Read from
Feature flag
tengu_event_sampling_config 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.0.54: 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.0.54. 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 {"tengu_api_after_normalize":{"sample_rate":0},"tengu_api_before_normalize":{"sample_rate":0},"tengu_api_cache_breakpoints":{"sample_rate":0.01},"tengu_plugin_name_collision":{"sample_rate":0.01},"tengu_query_after_attachments":{"sample_rate":0},"tengu_query_before_attachments":{"sample_rate":0},"tengu_session_file_read":{"sample_rate":0.01},"tengu_skill_file_changed":{"sample_rate":0},"tengu_sysprompt_block":{"sample_rate":0.01},"tengu_sysprompt_boundary_found":{"sample_rate":0.01},"tengu_sysprompt_missing_boundary_marker":{"sample_rate":0.01}} for tengu_event_sampling_config, 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 {"tengu_plugin_name_collision":{"sample_rate":0.01},"tengu_session_file_read":{"sample_rate":0.01},"tengu_skill_file_changed":{"sample_rate":0}} for tengu_event_sampling_config, 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 nothing at all, having stopped carrying it for tengu_event_sampling_config, 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 →

See this entry in the whole of v2.0.54 →

Feedback