[DOCS] Missing `CLAUDE_CODE_ENABLE_TELEMETRY` in Environment Variables Reference

Resolved 💬 3 comments Opened Jan 22, 2026 by coygeek Closed Jan 23, 2026

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

The "Environment variables" reference table located at the bottom of the Settings page.

Current Documentation

The "Environment variables" table currently lists DISABLE_TELEMETRY with the description:

Set to 1 to opt out of Statsig telemetry (note that Statsig events do not include user data like code, file paths, or bash commands)

However, the table omits CLAUDE_CODE_ENABLE_TELEMETRY.

What's Wrong or Missing?

The Monitoring documentation (https://code.claude.com/docs/en/monitoring-usage) explicitly states that to configure OpenTelemetry, the first step is:
export CLAUDE_CODE_ENABLE_TELEMETRY=1

However, this required variable is missing from the central "Environment variables" reference table in the Settings documentation. Users relying solely on the Settings page as a comprehensive reference will fail to configure OpenTelemetry correctly because they will not know this variable exists or that it is required.

Suggested Improvement

Please add a new row to the "Environment variables" table in https://code.claude.com/docs/en/settings with the following details:

| Variable | Purpose |
| :--- | :--- |
| CLAUDE_CODE_ENABLE_TELEMETRY | Enables OpenTelemetry data collection (required to use OTel metrics and logging). |

Impact

High - Prevents users from using a feature

Additional Context

  • Related Documentation: The variable is correctly referenced in the "Quick start" section of the Monitoring page here: https://code.claude.com/docs/en/monitoring-usage#quick-start
  • Discrepancy: The settings page currently only references disabling the default Statsig telemetry (DISABLE_TELEMETRY), but misses the variable required to enable the custom OTel integration.

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗