Source Intelligence

DisclaimerUnofficial, and not affiliated with Anthropic. Nearly all of this is read straight out of what ships: npm bundles, captured prompts, published docs. Anthropic's own notes go in verbatim, marked as theirs. The rest is my reading, and every entry carries the strings behind it. If one looks wrong, vote it down and say why.

All of v2.0.36 Home All releases olderv2.0.35 v2.0.37newer
Claude Code v2.0.36

Datadog Telemetry Integration

Feature flag
tengu_log_datadog_events On for this account, and not off by default

The flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.

This account: on · anonymous baseline: on · compiled default in v2.0.36: 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.36. It isn't a statement about your account. What a flag value here can and cannot tell you

What: New telemetry backend for event logging and monitoring Details:

  • Sends logs to Datadog HTTP intake endpoint: https://http-intake.logs.datadoghq.com/api/v2/logs
  • Controlled by feature gate tengu_log_datadog_events (gate name at line 477899)
  • Batches events for efficiency (batch size threshold KBI, flush interval VBI = 15000ms at line 477634)
  • Includes context tags: user type, version, model, session ID, platform details
  • Automatic flush on process exit
  • Evidence: FBI constant at line 477632, gate check er2 at line 477899, batching logic in QB0() at line 477567 and BB0() at line 477543

See this entry in the whole of v2.0.36 →