Remote Control fails: node: bad option: --sdk-url (v2.1.63)
Resolved 💬 3 comments Opened Mar 1, 2026 by jasonwilbur Closed Mar 5, 2026
Bug Description
claude remote-control fails immediately with a Node.js error indicating --sdk-url is being passed as a Node flag rather than a script argument.
Steps to Reproduce
- Run
claude remote-control - Type
yto enable - Session immediately fails
Error Output
[09:30:35] Session failed: /opt/homebrew/Cellar/node@20/20.20.0/bin/node: bad option: --sdk-url session_01BoGoyuaXNig4z8Gu5Nr28m
[09:30:35] To reconnect: claude --resume session_01BoGoyuaXNig4z8Gu5Nr28m
Environment
- Claude Code version: 2.1.63
- Node.js versions tested: 23.7.0 and 20.20.0 (both fail with same error)
- OS: macOS Sequoia (Apple Silicon / arm64)
- Install method: npm via Homebrew (
/opt/homebrew/lib/node_modules/@anthropic-ai/claude-code) - Plan: Max
Expected Behavior
Remote Control should start, display a session URL and QR code, and allow connecting from a browser or mobile device.
Notes
The error suggests --sdk-url <session_id> is being passed directly to the node binary as a flag (before the script path), rather than as an argument to the Claude Code script. This causes Node.js to reject it as an unknown option. Tested on two different Node.js versions (20 and 23) with identical results.
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗