Remote Control unavailable on Windows Server 2025 (VMware VM): tengu_bridge_client_presence_enabled persistently false

Description

The Remote Control feature is not available in Claude Code on my machine. The GrowthBook feature flag tengu_bridge_client_presence_enabled is consistently false on this environment, while the same Anthropic account has it set to true on other platforms (macOS).

/doctor dismisses without showing Remote Control as available or offering any diagnostic information about it.

Environment

| Item | Value |
|------|-------|
| Claude Code version | 2.1.101 |
| OS | Windows Server 2025 Standard Evaluation (10.0.26100) |
| Platform | VMware VM (Intel x64) |
| Install method | native |
| Auth method | oauth_token |
| Subscription | Active (Pro/Max) |

Relevant feature flags (from cachedGrowthBookFeatures in .claude.json)

tengu_bridge_client_presence_enabled: false   ← blocks Remote Control
tengu_bridge_repl_v2:                 true
tengu_copper_bridge:                  true
tengu_bridge_repl_v2_config:          configured (min_version: 2.1.70)
tengu_bridge_poll_interval_ms:        0
tengu_ccr_bridge:                     false

Steps to reproduce

1. Install Claude Code 2.1.101 natively on Windows Server 2025 (VMware VM)
2. Authenticate with an account that has Remote Control available on macOS
3. Run /doctor — no Remote Control option shown
4. Inspect cachedGrowthBookFeatures in .claude.json — tengu_bridge_client_presence_enabled is false

Expected behaviour

Remote Control should be available (or at minimum, explicitly flagged as unsupported on this platform).

Additional notes

• The flag has been observed as false across multiple sessions and GrowthBook cache refreshes — it is not a stale cache issue.
• The same account has tengu_bridge_client_presence_enabled: true on macOS (Parallels/M2).
• The machine is a domain-joined Windows Server 2025 VM used as an admin workstation (Active Directory / infrastructure management).
• numStartups: 28 — this is not a first-run issue.