Skip to content
BENIBIX Learn

DISABLE_TELEMETRY vs CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC

People think DISABLE_TELEMETRY stops all that Claude Code sends home. It stops only usage data and flags. Crash reports, updates, release notes and /feedback still go out. The NONESSENTIAL_TRAFFIC switch stops all of those at once. Only calls to the model are left. Use the first for privacy, and the second for a locked network.

AI⌨️ Claude Code

DISABLE_TELEMETRY

Any value stops the usage data sent home.

DISABLE_TELEMETRY stops the usage data Claude Code sends home. Any value turns it on, even 0 or false. To send data again, unset it. It also stops the fetch of feature flags. DO_NOT_TRACK=1 does the same, but there 0 means send.

Example
Jack's company does not allow tools to report usage. He sets this in managed settings, so no laptop sends it.
Why it matters
Some firms must keep tools from reporting home. This is the switch for that.
Full entry
AI⌨️ Claude Code

CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC

Any value cuts each call Claude Code can do without.

CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC stops each call Claude Code can do without. That means updates, usage data, crash reports, /feedback, release notes and flags. Any value turns it on, even 0. Calls to the model still go out. A few things that need flags stop, such as Remote Control.

Example
Jack's firewall allows only the model's address. Every other call failed slowly. He sets this, and Claude Code stops trying them.
Why it matters
On a locked network, it ends slow failed calls. It is also the one switch for a strict privacy rule.
Full entry

In one line

DISABLE_TELEMETRY
Any value stops the usage data sent home.
CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC
Any value cuts each call Claude Code can do without.