Remote Control unavailable — feature flag tengu_onyx_plover.remoteEnabled is false, no toggle shown in VS Code extension

Description

Remote Control (control session from claude.ai/code or the Claude mobile app) has stopped being available. It previously worked (account history shows a prior "Claude Code Remote" connection), but it no longer appears anywhere in the UI.

Environment

• Claude Code native CLI: 2.1.219 (commit 7006c4c3acac)
• VS Code extension: anthropic.claude-code 2.1.270
• Platform: Windows 11 (win32-x64)
• Install method: native

Steps taken

1. Checked claude.ai account settings (General/Account/Claude Code sections) — no Remote Control toggle found anywhere.
2. Checked VS Code extension input bar area where the Remote Control indicator normally shows — not present.
3. Ran claude doctor — found and removed a leftover npm-global install (@anthropic-ai/claude-code@2.1.161) that was conflicting with the native install. This cleared a warning but did not restore Remote Control.
4. Restarted VS Code after cleanup — still no Remote Control toggle.
5. Inspected ~/.claude.json cached feature flags and found:

``
"tengu_onyx_plover": {"enabled": false, "minHours": 24, "minSessions": 3, "remoteEnabled": false}
``
This flag was freshly fetched (timestamp matched the moment of inspection, not stale cache), indicating the server is currently returning Remote Control as disabled for this account.

Expected behavior

Remote Control should be available/toggleable, since claudeAiMcpEverConnected in local config shows it was connected before ("claude.ai Claude Code Remote").

Actual behavior

No Remote Control toggle appears anywhere in claude.ai settings or the VS Code extension. The tengu_onyx_plover feature flag returns remoteEnabled: false for this account.

Request

Could someone check server-side why this account's Remote Control eligibility flag flipped to disabled after previously being connected/working?