Unclear What the earlier empty answer led to in practice is not settled.
What
Remote Control lets you drive a Claude Code session on your machine from somewhere else. Claude Code normally decides whether you may use it by asking Anthropic's feature-flag service, the remote switchboard that turns features on and off, about a flag called tengu_ccr_bridge. If you turn telemetry off, that service is not contacted, so the question could not be answered. Telemetry is the usage data Claude Code sends back. This release changes what happens in that case in two ways.
- A new early pass in the eligibility check lets Remote Control through without the
tengu_ccr_bridgeflag. The eligibility check is the step that decides whether you may use Remote Control. The pass runs before the checks for feature-flag evaluation and the flag. It applies only when all of these hold:- telemetry is off through
DISABLE_TELEMETRYorDO_NOT_TRACK. SettingCLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICdoes not count. DISABLE_GROWTHBOOKis not set.- you are a first-party user who belongs to an organisation.
- you are signed in with OAuth, the browser sign-in, on a pro, max, team or enterprise plan.
- telemetry is off through
- The eligibility check, the doctor-style connectivity list and the startup check all accept this path. Before, these users were refused with
flags_disabled. - Remotely started sessions have a minimum required version, called the floor. When that floor cannot be fetched and
DISABLE_TELEMETRYorDO_NOT_TRACKis set, Claude Code now refuses with the reasonfloor_unreachableand a message explaining that the required version cannot be received while feature-flag evaluation is off. Before, it returned no reason at all in that case.
Why
Paying subscribers who opted out of telemetry were shut out of Remote Control only because the flag service could not be reached. They can now get past the eligibility check. If you have telemetry off, a remotely started session can still be refused when its minimum version cannot be fetched, and you are now told why instead of getting no explanation.
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
`DO_NOT_TRACK`, set to any value other than `0` or `false`, turns usage analytics and error reports off. It is the same switch as `disable_telemetry = true` in the configuration file. `GITHUB_TOKEN` (or `GH_TOKEN`) is optional and is used …claude-science/command-line-settings see the edit
| **Metrics** | Default on.<br />`DISABLE_TELEMETRY=1` to disable. | Default off.<br />`CLAUDE_CODE_USE_VERTEX` must be 1. | Default off.<br />`CLAUDE_CODE_USE_BEDROCK` must be 1. | Default off.<br />`CLAUDE_CODE_USE_FOUNDRY` must be 1. | …data-usage see the edit
Claude Code sends two kinds of operational telemetry: usage metrics and error reports. You can turn each off individually with the environment variables below, or disable all non-essential traffic at once by setting `CLAUDE_CODE_DISABLE_NO…data-usage see the edit
What the earlier empty answer led to in practice is not settled.
A small documentation edit on Data usage touched a line naming DISABLE_TELEMETRY after this was published.
Fixed Remote Control being unavailable on paid plans when telemetry is turned off with DISABLE_TELEMETRY or DO_NOT_TRACK