[BUG] DISABLE_TELEMETRY=1 breaks remote-control with misleading "not yet enabled" error

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Bug Description

claude remote-control fails with "Error: Remote Control is not yet enabled for your account" when DISABLE_TELEMETRY=1 is set — even on an eligible account.

## Steps to Reproduce

1. DISABLE_TELEMETRY=1 claude remote-control
2. Observe: "Error: Remote Control is not yet enabled for your account"
3. claude remote-control (without the variable)
4. Observe: works correctly

## Expected Behavior

DISABLE_TELEMETRY should disable analytics/tracking only. It should not affect feature-gate evaluation for Remote Control.

## Environment

• Claude Code: 2.1.63
• OS: Linux (Ubuntu)

What Should Happen?

DISABLE_TELEMETRY should disable analytics/tracking only. It should not affect feature-gate evaluation for Remote Control.

Error Messages/Logs

DISABLE_TELEMETRY=1 claude remote-control
Error: Remote Control is not yet enabled for your account.
❯ claude remote-control

·✔︎· Connected

Steps to Reproduce

DISABLE_TELEMETRY=1 claude remote-control
claude remote-control

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.63 (Claude Code)

Platform

Anthropic API

Operating System

Ubuntu/Debian Linux

Terminal/Shell

Other

Additional Information

_No response_