"claude remote-control" CLI subcommand fails on Windows with "bad option: --sdk-url"

Bug Description

Running claude remote-control (or claude rc) directly from the terminal before starting a Claude Code session fails with the following error on Windows:

Session failed: C:\Program Files\nodejs\node.exe: bad option: --sdk-url
To reconnect: claude --resume session_01CEuAukqwBbXHLSARSb1Sit

However, using /remote-control (or /rc) from within an active Claude Code session works perfectly fine.

Additionally: QR code not displayed

When /remote-control is activated from within a session, only the session URL is shown. The QR code (for easy phone access) does not appear. Pressing spacebar does not toggle QR code display either.

Steps to Reproduce

Issue 1: CLI subcommand failure

1. Open a terminal (PowerShell or Windows Terminal)
2. Run claude remote-control or claude rc
3. Error: Session failed: C:\Program Files\nodejs\node.exe: bad option: --sdk-url

Issue 2: Missing QR code

1. Start Claude Code normally with claude
2. Run /remote-control from within the session
3. Session URL is displayed, but no QR code appears

Expected Behavior

1. claude remote-control should start remote control directly from the terminal without needing to first launch Claude interactively
2. QR code should be displayed alongside the session URL for easy mobile access

Workaround

Start Claude Code first (claude), then use /remote-control within the session. Remote control itself works fine this way (minus the QR code).

Environment

• OS: Windows 11 Pro (10.0.26200)
• Claude Code version: v2.1.59
• Terminal: Windows Terminal (PowerShell)
• Node.js: Installed at C:\Program Files\nodejs\node.exe