[BUG] remote-control fails with bad option --sdk-url

Bug Description

claude remote-control immediately fails with bad option: --sdk-url on every attempt.

Error Output

[12:13:04] Session started: "Session session_01UKiD8bXqsgREXCwzH6QrSS" (session_01UKiD8bXqsgREXCwzH6QrSS)
[12:13:04] Debug log: /var/folders/sg/18mjz1ss55z9qr36sf9x2vvc0000gn/T/claude/bridge-session-session_01UKiD8bXqsgREXCwzH6QrSS.log
[12:13:04] Session failed: /Users/yashsolanki/.nvm/versions/node/v20.16.0/bin/node: bad option: --sdk-url session_01UKiD8bXqsgREXCwzH6QrSS
[12:13:04] To reconnect: claude --resume session_01UKiD8bXqsgREXCwzH6QrSS
[12:13:05] Failed to archive session session_01UKiD8bXqsgREXCwzH6QrSS: Not Found
[12:13:06] Environment deregistered.
[12:13:06] Environment offline.
Root Cause

It appears --sdk-url is being passed as a Node.js runtime flag rather than as an application argument to Claude Code. Node doesn't recognize --sdk-url and exits immediately.

Environment

Claude Code version: 2.1.56
Node.js: v20.16.0 (also tested with v24.14.0 — same error)
OS: macOS (Darwin 25.2.0)
Node manager: nvm
Plan: Max
Auth: logged in via /login
Steps to Reproduce

cd into any project directory
Run claude remote-control (or claude remote-control --verbose)
Session starts and immediately fails
Expected Behavior

Remote Control session should start and display a session URL and QR code for connecting from another device.

Actual Behavior

Session spawns, then immediately crashes with bad option: --sdk-url.