{"version":"2.1.283","anchor":"remote-sessions-refused-with-an-explicit-reason-when-telemet","canonical_anchor":"remote-sessions-refused-with-an-explicit-reason-when-telemet","heading":"Remote Control changes for users who turned telemetry off","tier":"notice","area":"Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/remote-sessions-refused-with-an-explicit-reason-when-telemet","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### Remote Control changes for users who turned telemetry off\n\nPaid 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\n\n**Unclear.** What the earlier empty answer led to in practice is not settled.\n\n**What**\n\nRemote 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.\n\n- 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: telemetry is off through `DISABLE_TELEMETRY` or `DO_NOT_TRACK`. Setting `CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC` does not count.\n\n- `DISABLE_GROWTHBOOK` is not set.\n\n- you are a first-party user who belongs to an organisation.\n\n- you are signed in with OAuth, the browser sign-in, on a pro, max, team or enterprise plan.\n\n- The eligibility check, the doctor-style connectivity list and the startup check all accept this path. Before, these users were refused with `flags_disabled`.\n\n- 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.\n\n**Why**\n\nPaying 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.\n\n- Area: Sessions\n- Names: `DISABLE_TELEMETRY`, `DO_NOT_TRACK`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}