/remote-control not available on WSL2 - feature flag tengu_ccr_bridge set to false

Description

The /remote-control slash command is not available on WSL2, even though the same Max account works correctly on another computer (non-WSL).

Environment

• Claude Code version: 2.1.76
• Install method: native
• OS: Linux 6.6.87.2-microsoft-standard-WSL2 (WSL2 on Windows)
• Shell: zsh
• Account: Max subscription (stripe_subscription), authenticated via OAuth

Steps to reproduce

1. Install Claude Code v2.1.76 on WSL2
2. Authenticate with /login using a Max subscription account
3. Type /remote-control → shows "command not found"
4. On a different computer (non-WSL) with the same account → /remote-control works fine

Investigation

After debugging, I found the root cause: the server-assigned feature flag tengu_ccr_bridge is set to false in ~/.claude.json → cachedGrowthBookFeatures for this WSL2 installation.

• Manually changing it to true gets overwritten by the server on next startup
• Deleting ~/.claude.json and re-authenticating still results in tengu_ccr_bridge: false
• The same account on a non-WSL machine gets tengu_ccr_bridge: true

This suggests the feature flag rollout may be excluding WSL2 environments or there's a device-level targeting issue.

Expected behavior

/remote-control should be available on WSL2 for Max subscribers, same as on other platforms.

Workaround attempted

• /logout + /login → no change
• Deleting ~/.claude.json + fresh login → no change
• Manually editing tengu_ccr_bridge to true → overwritten by server on restart