[BUG] remote-control session fails on Windows: "node.exe: 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?

claude remote-control connects successfully and outputs a session URL, but the session immediately fails with a node.exe: bad option error.

## Environment

• OS: Windows 11 Pro 10.0.26200
• Claude Code: v2.1.58 (installed globally via npm)
• Node.js: Located at C:\Program Files\nodejs\node.exe
• Shell: Git Bash

What Should Happen?

## Expected Behavior

Session should remain connected and be accessible from claude.ai/code or the Claude mobile app.

Error Messages/Logs

## Actual Behavior

  ·✔︎· Connected · agent-desk · master

  Continue coding in the Claude app or https://claude.ai/code/session_0184nAJfVA5naFtAD7QtZi7V?bridge=env_011MGS9CXcuNiDggFdXvZGBD
  space to show QR code

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

  It appears the CLI is passing `--sdk-url` as a flag to `node.exe` rather than the Claude runtime when spawning the session subprocess.

Steps to Reproduce

## Steps to Reproduce

1. Run claude remote-control from a project directory on Windows
2. CLI connects and outputs a session URL (https://claude.ai/code/session_...)
3. Within seconds, session fails

Claude Model

None

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.58

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

## Environment

• OS: Windows 11 Pro 10.0.26200
• Claude Code: v2.1.58 (installed globally via npm)
• Node.js: Located at C:\Program Files\nodejs\node.exe
• Shell: Git Bash