[BUG] Session failed: bad option: --sdk-url when using claude with remote control on Node.js v25

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?

Session failed: bad option: --sdk-url when using claude with remote control on Node.js v25

Labels: bug

Description

When starting a Claude Code session with the remote control feature enabled, the session immediately crashes. Node.js rejects --sdk-url as an unrecognized flag. Normal claude sessions (without remote control) work fine.

What Should Happen?

Remote control sessions should start normally on Node.js v25.

Error Messages/Logs

Session failed: /opt/homebrew/Cellar/node/25.2.1/bin/node: bad option: --sdk-url session_01LA7jKyhJj3FZegkxynhGh3
[18:53:11] To reconnect: claude --resume session_01LA7jKyhJj3FZegkxynhGh3

Steps to Reproduce

Steps to Reproduce

1. Install Node.js v25.2.1 via Homebrew
2. Install Claude Code v2.1.63
3. Start a session with remote control enabled (e.g., claude --remote-control or equivalent)
4. Session fails immediately with the above error

Regular sessions without remote control do not exhibit this issue.

Claude Model

Opus

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

2.1.63

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

IntelliJ IDEA terminal

Additional Information

Additional Context

• The --sdk-url flag does not appear in claude --help output, suggesting it's an internal flag used by the remote control subsystem.
• Standard claude sessions work correctly on the same Node.js version.
• Resuming with claude --resume <session_id> doe