Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.283 ·

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

Group of 3 You'll notice Bug Fixes
JSON All of v2.1.283
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
Remote ControlArea: what it touches
Bug FixesKind: 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:
  • 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.

Read from
Feature flag
tengu_ccr_bridge Off by default, switched on for this account

The shipped code defaults this off, and the flag server returned on for the one account this site reads on this version. That is the reading that makes the entry above worth a second look, and it still says nothing about your account.

This account: on · anonymous baseline: off · compiled default in v2.1.283: off

These values were read against a different version of Claude Code, so treat them as the nearest reading available instead of one taken on this release.

Read once, for one account on one subscription tier, against v2.1.283. It isn't a statement about your account. What a flag value here can and cannot tell you

How sure we are
One source agreesOne thing we can check says the same as this entry.
Anthropic's release notes agreeFixed Remote Control being unavailable on paid plans when telemetry is turned off with DISABLE_TELEMETRY or DO_NOT_TRACK

See this entry in the whole of v2.1.283 →

Feedback