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

Bug Description

claude remote-control immediately fails with a Node.js error: bad option: --sdk-url. The session starts but crashes on spawn, suggesting --sdk-url is being passed as a Node.js flag instead of an application argument.

Steps to Reproduce

claude remote-control --verbose

Actual Behavior

Remote Control v2.1.55
Max concurrent sessions: 1
Environment ID: env_01Anetr4qssRYa5cAKFdy19R

[13:18:38] Session started: "Session session_01Gmy7eSHd4jc7tXDZTxbZ4m" (session_01Gmy7eSHd4jc7tXDZTxbZ4m)
[13:18:38] Debug log: /var/folders/.../bridge-session-session_01Gmy7eSHd4jc7tXDZTxbZ4m.log
·✔︎· Connected · invoice · develop
[13:18:38] Session failed: /Users/.../.nvm/versions/node/v22.17.0/bin/node: bad option: --sdk-url session_01Gmy7eSHd4jc7tXDZTxbZ4m
[13:18:38] To reconnect: claude --resume session_01Gmy7eSHd4jc7tXDZTxbZ4m
[13:18:38] Failed to archive session session_01Gmy7eSHd4jc7tXDZTxbZ4m: Not Found
[13:18:39] Environment deregistered.
[13:18:39] Environment offline.

Expected Behavior

The remote-control session should start and remain connected, waiting for incoming commands.

Environment

• Claude Code version: 2.1.55
• Installation method: npm global (npm install -g @anthropic-ai/claude-code)
• Node.js version: v22.17.0 (via nvm)
• OS: macOS 26.3 (Build 25D125)
• Architecture: arm64 (Apple Silicon)

Analysis

It appears that --sdk-url is being passed as a Node.js CLI flag (before the script path) rather than as an argument to the Claude Code application. Node.js does not recognize --sdk-url as a valid V8/Node option, causing immediate termination.