Enable Telemetry Blueprint

Standard telemetry enablement setting that activates Claude Code usage analytics for product improvements and performance insights.

When to Use This Setting

Apply this setting when you need to:

• Contribute anonymized usage data to help Anthropic improve Claude Code features and performance
• Enable session analytics that provide insights into your own usage patterns and tool effectiveness
• Restore default telemetry collection after it was previously disabled Consider alternatives when:
• Your organization prohibits sending usage data to external services
• You are in an air-gapped environment where telemetry connections would fail or be blocked

Quick Start

Configuration

Copy
name: enable-telemetry-blueprint
type: setting
category: telemetry

Example Application

Copy
claude setting:apply enable-telemetry-blueprint

Example Output

Setting applied. Changes:
- CLAUDE_CODE_ENABLE_TELEMETRY: 1
- telemetry_collection: enabled
- data_scope: anonymized usage analytics
- transmission: default OTEL pipeline

Core Concepts

Enable Telemetry Overview

Aspect	Details
Telemetry Flag	CLAUDE_CODE_ENABLE_TELEMETRY set to 1, activating default collection
Data Scope	Anonymized usage patterns, session duration, feature utilization metrics
Privacy	No source code, file contents, or personally identifiable information collected
Transmission	Uses default OpenTelemetry pipeline to the standard Claude Code metrics endpoint
Purpose	Helps improve Claude Code features, detect bugs, and optimize performance

Enabled Telemetry Architecture

+-------------------+     +---------------------+     +------------------+
| Claude Code       |---->| Telemetry Collector |---->| OTEL Pipeline    |
| runtime events    |     | ENABLE_TELEMETRY=1  |     | default exporter |
| feature usage     |     | serialize metrics   |     | metrics endpoint |
+-------------------+     +---------------------+     +------------------+
                                   |                          |
                                   v                          v
                          +---------------------+    +------------------+
                          | Anonymizer          |    | Analytics Backend|
                          | strip PII           |    | aggregated data  |
                          | hash identifiers    |    | product insights |
                          +---------------------+    +------------------+

Configuration

Parameter	Type	Default	Description
CLAUDE_CODE_ENABLE_TELEMETRY	string	"1"	Master switch enabling all telemetry collection
telemetry_scope	string	"usage"	Scope of data collection: usage, performance, or full
anonymize	boolean	true	Strip personally identifiable information before transmission
batch_interval	integer	60	Seconds between batched telemetry transmissions
retry_on_failure	boolean	true	Retry failed telemetry transmissions on next batch cycle

Best Practices

1. Review the privacy policy - Before enabling telemetry, review Anthropic's data collection policy to understand exactly what data is collected and how it is used. This ensures informed consent and compliance with your organization's data policies.
2. Enable selectively per environment - Consider enabling telemetry only in development environments and disabling it in CI/CD pipelines where the telemetry data would be less useful and could slow down automated workflows.
3. Monitor network impact - Telemetry transmission uses minimal bandwidth, but verify it does not interfere with your development workflow, especially on metered or slow network connections.
4. Use as a troubleshooting aid - Enabled telemetry can help Anthropic support diagnose issues you report. If you experience bugs, having telemetry active provides context that speeds up issue resolution.
5. Coordinate with team settings - If some team members have telemetry disabled while others have it enabled, the collected data may not represent your full team usage pattern. Align the setting across the team for consistent data.

Common Issues

1. Telemetry still disabled after applying - A previously set CLAUDE_CODE_ENABLE_TELEMETRY=0 in your shell profile may override this setting. Check ~/.zshrc or ~/.bashrc for conflicting environment variable exports.
2. Network errors in telemetry logs - Firewall rules or proxy settings may block outbound connections to the telemetry endpoint. Ensure your network allows HTTPS connections to Anthropic's telemetry infrastructure.
3. No visible impact after enabling - Telemetry operates silently in the background. There is no visible indicator in the UI confirming data collection. The setting takes effect immediately upon applying.