Remote Control fails on Windows: node.exe bad option --sdk-url

Bug Description

claude remote-control fails immediately after accepting the prompt on Windows. Node.js interprets --sdk-url as a Node option rather than passing it to the Claude Code application.

Error Output

PS C:\Projects\Work> claude remote-control

Remote Control lets you access this CLI session from the web (claude.ai/code)
or the Claude app, so you can pick up where you left off on any device.

You can disconnect remote access anytime by running /remote-control again.

Enable Remote Control? (y/n) y

[16:47:30] Session failed: C:\Program Files\nodejs\node.exe: bad option: --sdk-url session_01PKXLT1zu7uGyLzCL5b1Bnn
[16:47:30] To reconnect: claude --resume session_01PKXLT1zu7uGyLzCL5b1Bnn

Environment

• Claude Code version: 2.1.63
• OS: Windows 11 Pro (10.0.26200)
• Node.js version: v24.12.0
• Shell: PowerShell
• Install method: npm global (npm install -g @anthropic-ai/claude-code)

Steps to Reproduce

1. Run claude remote-control
2. Accept the "Enable Remote Control?" prompt with y
3. Session immediately fails with the bad option: --sdk-url error

Expected Behavior

Remote Control session should start successfully and display a session URL / QR code.

Analysis

It appears the subprocess is being spawned in a way that passes --sdk-url as a flag to node.exe itself rather than as an argument to the Claude Code entry script. This may be a Windows-specific issue with how the .cmd shim or process spawning handles arguments.