Remote Control changes for users who turned telemetry off
Paid subscribers with telemetry off can pass Remote Control's eligibility check, but remote sessions now refuse with a clear reason when the version floor is unreachable
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
SessionsArea: what it touches
ImprovementsKind: in v2.1.283,
ImprovementsSection of the release
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_bridge flag. 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:
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.
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_TELEMETRY or DO_NOT_TRACK is set, Claude Code now refuses with the reason floor_unreachable and 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.
Added sinceA small documentation edit on Data usage touched a line naming DISABLE_TELEMETRY after this was published.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-usagesee the edit
How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtWhat the earlier empty answer led to in practice is not settled.
Anthropic's documentation agreesA small documentation edit on Data usage touched a line naming DISABLE_TELEMETRY after this was published.
Anthropic's release notes agreeFixed Remote Control being unavailable on paid plans when telemetry is turned off with DISABLE_TELEMETRY or DO_NOT_TRACK