claude remote-control fails with bad option: --sdk-url

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Connection appears successful initially, then immediately fails:
Session failed: C:\Program Files\nodejs\node.exe: bad option: --sdk-url session_01QDXX3nmTfGVbxQsxEZNnWS
To reconnect: claude --resume session_01QDXX3nmTfGVbxQsxEZNnWS

What Should Happen?

Local Claude Code session spawns and connects to the remote bridge.

Error Messages/Logs

[21:28:05] Session failed: C:\Program Files\nodejs\node.exe: bad option: --sdk-url session_01UCeRHsb6eMmhLfJbRnGoFj
[21:28:05] To reconnect: claude --resume session_01UCeRHsb6eMmhLfJbRnGoFj

Steps to Reproduce

1. Run claude remote-control in any directory
2. Open the generated URL in claude.ai/code
3. Claude.ai attempts to connect back to the local session

Claude Model

Sonnet (default)

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

Claude Code: v2.1.63

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

• Node.js: v24.13.1
• OS: Windows 11
• Root cause (likely):When claude.ai/code triggers the local session spawn, Claude Code passes --sdk-url directly to node.exe instead of to the Claude Code binary/script. Node.js v24 does not recognize --sdk-url as a valid option and exits immediately.

The correct invocation should likely be:
claude --sdk-url <session_url>
or similar, not node.exe --sdk-url