Clarification needed on Statsig dependency following OpenAI acquisition

Title: Clarification needed on Statsig dependency following OpenAI acquisition

Labels: question, discussion, external-dependency, documentation

Body

To the Anthropic Claude Code Team,

First off, thanks for creating such a powerful and useful tool.

I'm opening this issue to request some clarification regarding Claude Code's dependency on Statsig, in light of the recent news that OpenAI has acquired Statsig (as of September 2, 2025).

Background

The official Claude Code documentation explicitly states that Statsig is used for operational telemetry.

From the data-usage documentation page:

Claude Code connects from users' machines to the Statsig service to log operational metrics such as latency, reliability, and usage patterns. This logging does not include any code or file paths... To opt out of Statsig telemetry, set the DISABLE_TELEMETRY environment variable.

Additionally, the corporate-proxy documentation requires allow-listing statsig.anthropic.com, indicating it's a core service dependency.

The Issue

The acquisition of Statsig by OpenAI places a key operational dependency for Claude Code under the ownership of a direct competitor. While OpenAI's announcement states that "Statsig... will continue operating independently and serving its customer base," this situation raises several important questions for users, especially in enterprise environments where data privacy and supply chain stability are critical concerns.

This creates uncertainty about the long-term viability and data handling practices of this integration.

Questions for the Team

Could the team please provide some clarity on the following points?

1. Immediate Data Privacy: Are there any immediate changes to how Claude Code's telemetry data is handled by Statsig post-acquisition? What assurances can be provided that this operational data will remain fully firewalled from OpenAI?
2. Long-Term Roadmap: What is Anthropic's long-term strategy for this dependency? Is there a plan to migrate away from Statsig to an in-house or neutral third-party solution? If so, what is the anticipated timeline?
3. User Action & Best Practices: Do you recommend that security-conscious users and organizations begin using the DISABLE_TELEMETRY environment variable by default until there is a clear migration plan?
4. Relation to OpenTelemetry: The documentation for monitoring-usage details a comprehensive OpenTelemetry (OTel) integration. Is this OTel pipeline intended to be the long-term replacement for the Statsig integration?

Gaining clarity on this would be incredibly helpful for planning, security reviews, and continuing to advocate for the adoption of Claude Code within our organization.

Thank you for your transparency and for all the work you do on this product.